[EricH]

Because, with 5 weeks to plan and get ready (and presumably knowing all the ratios between where their encoder is and where the wheel is that it's tracking), they STILL complain when they only get a week to test the robot and implement the minor tweaking that should take 3 days at most.

Oh, and if a mechanical guy makes a minor error, the robot can still work. If a programmer makes a minor error in the wrong place, the robot doesn't work...

(Mechanical guy joking about good reasons not to take the blame)

Oh, and Bongle--

If both sub-teams can work together rather than fighting over whose bug it is, then you should have a more successful robot.

I'm sorry, but the mechanical bugs immediately get squashed by the nearest flyswatter. The programming team is therefore the only team that has bugs... But yes, in principle it is best to work together to find the problem and eliminate it.