Quote:
Originally Posted by Imperium283
This is one of the most reasonable ones most of all. I wish our team had that tone, that building is the priority, but we don't know how to set that tone. And when we try, it backfires on us socially
|
To be totally honest, we were a hardcore team that spent any spare time we had holed up with a laptop or the robot. We made it as far as we could considering the resources we had, it's unfortunate we didn't have more time. And, for a small team that basically taught oursevles robotics with no sponsors and a mentor who was learning with us, we did a hella good job.
Quote:
Originally Posted by DonRotolo
We have a strict "no gaming" policy during work hours. We enforce it reasonably well - not perfect, but we call it out when we see it (and we do look for it).
|
We allowed it seeing as how the programmers would sit bored for hourrrrrs while the engineers fixed something. Then when the programming came, 2 second fix and they went back to magic or minecraft.
__________________

Engineers vs. Programmers:
Engineers: If it's not on fire, it's a programming error.
Programmers: If it compiles, it's a hardware error.