[Butter's]

1. We split our members into there best area of interest. Some would rather do back-end, while some prefer doing autonomous.

2. Whiteboards & Paper are the best way to get ideas down & plan things out.

3. The best I can suggest is in the start, focus your time on preparation. Getting your laptop imaged, setting up the work environment, etc. Once your team knows how your going to approach the game, start planning how the team is going to tackle it from the code. After that you can't do much until you have a robot you can deploy too. If you have a lot of extra time, now is the chance to mess around with the old robot & refresh yourself with coding, api, etc

4. As suggested, Github is a great tool for storing your code / implementing version control. If your just making presentations or documents I'd go with Google Drive. It works the same as Dropbox, but has a great editor online to make Documents, Presentations, Spreadsheets, etc. It's all accessible online & via desktop (Once you download the application).

5. Try new things & experiment! This year I wanted to see if we could switch to Java. During the process I ran into a ton of issues, but I learned a ton from fixing them. Even if you don't end up using what you experiment with, it's always a fun new challenge, and can sometimes provide you with great knowledge you might need one day.