This year is our first year that we are able to have official team leads, and as I was perusing First Choice, I noticed the incredible wiring diagrams, I thought it would be wonderful to have something like that for our new programmers.
Does anyone display or share any tips sheets with their programming teams?
Has anyone stumbled across any they consider to be valuable?
Most of our team members come to us with a background in block programming (Scratch, and Lego mostly), so I feel for us, syntax, basic statements, and formatting would be the biggest help.
We have switched from Python to Java, but I see us possibly switching back to Python this year depending on how things pan out in our off-season work.
I find W3Schools super helpful when students need a quick refresher on how something is formatted. It also is a nice intro into them reading documentation.
Thanks. As do I, I was thinking some reference that people could just see (also not cut and paste from). Perhaps it is the old school teacher in me, but I feel a quick reference along with sources like w3schools, could help people learn quickly.
Obviously, in order to put everything on it, it would need to be as long as the w3 school’s site.
I am also considering working with our team lead to create a team style guide for naming conventions to avoid the…
FrontLeftDrive
frontLeftDrive
front_left_drive
etc.
…issue. That may be better as a quick reference.
Thank you. Those are great. While the first is not really different than the W3Schools, it does seem more concise which is what I was looking for.
I love the Google one as well. I think I am really looking for two things, and those seem to each be one.
I think the thing that happened(or happens when I learn new code) to me when learning a new programing language (or when I went from block to text-based programing), was I knew the logic I wanted to implement, and could write it in pseudo code or a language I am more familiar with, but did not know the syntax. I have seen that happen with students too.
I am thinking basic; a quick reference for things like…
*General rules to keep in mind syntactically
*Specific operators
*How do I instantiate a variable
*How do I write basic statements (If, for, switch)
That sort of thing.
The last is really important, because if you do not craft the statements correctly, the errors may not happen where you would expect.
There are hundreds of “quick” references and they would all suffer from not being exactly what you want. Consider hacking up a couple of them for your customization.
If you want very brief, these two are two different levels of brief. They, like most, also, suffer from having up to half of their content being of no use to you for robot code.
However, it’s also perfectly fine to just get it set up in your repo and, periodically, have students run it. Gotta be a bit careful about merge conflicts, but it’s not too bad to resolve them and re-run the formatter after the fact.