Quote:
Originally Posted by Sperkowsky
We use github also. I'm not trying to offend the news people but to our team coding simple driving (tank mecanum omni ect) is something that take max 20 minutes and to program the lift another maybe 15. If that's not everyone I feel bad and we will help but it shouldn't be an issue for them to come back easily. I'd be more mad they just lost a 500-1000 piece of hardware.
|
True, but in the stress of competition.. You're right though, assuming a fairly standard drive train and mechanisms, it would not take long to take the sample robot code and turn it into a basic driving robot. You would lose your autonomous code and any mechanism state machines though.
Quote:
Originally Posted by dtengineering
A USB key of "known good" software taped to the driver station.
Github, Dropbox, Google Drive... none of them will help if you drop your laptop half-way through re-programming your robot, while you're standing in the queueing line.
|
Yes, my backup strategy would be, GitHub for all development, then a USB stick with the code, and a backup laptop.
GitHub works well but there is a bit of a learning curve, especially when multiple people are working in the same repo at the same time. People fork their own and make their changes and then make pull requests, but they should also pull often to keep theirs up to date. It takes some time to get used to the concept of version control, branches, forks, pushes, pulls, etc.
We were at a point in my team where the kids got in the habit of calling "MERGE!" when they were committing code. Everyone else in the room would yell it back, like a herd of mooing cattle. When we voted to name our robot, "MERGE" got second place!