[Tassemet]

Originally Posted by SuperNerd256

There are times when our programmers do have free time (which I don't see why there would be, unless they can do their work in less than 6 weeks). During this "Free time", they play some games until they're needed. Our programmers are for the most part responsible, and in the end get their work done. One of the major problems here is while they're responsible and do their work, the games distract everyone else, making the team unproductive.

So while your programmers somehow have hourrrrrs of free time, I can tell you from experience that sometimes it's best to cut the games for the team's sake, and for the sake of productivity. Anyways, they're programmers for robot's sake! Tell them to go outside for once!

Bro tip: Tell them outside has really good graphics!

To be totally honest they had the code already ready to run before we even got into the build session. I'm talking FTC so hang with me But we had the same issues with one hour becoming ten and them waiting is not a good thing. To be totally honest as well, these were the kids who couldn't advance any further programming wise in a high school setting, as the three we had already were making their own games and using programming to do whatever they wanted/needed. I mean these guys finished AP classes worth of programming in 3/4 the time required to do it( since ap programming is self paced at our school) so the games were there to keep them occupied. Nowm that didn't distract the rest of us, because the rest of us were worried about the next bloody finger (yeah guilty) and getting our building part done on time.