why blame the programmers??

[FRC4ME]

Originally Posted by LukeS

What bothers me is when we know it can't be code for whatever reason (see the 2nd part of my above post), and people still insist it is. When I say, ``Look, trust me, I have considered this. It's not code.'' please trust me. I know what I'm talking about. Sure I'll check it again, but that's not going to be it, so don't waste both of our time, have someone else be checking other stuff too. Don't make them move so I can prove to you that it is not code.

Lol. Earlier this year the programmers experienced this on my team. One of the drivers insisted that the left joystick of the tank steering was causing both sides of the tank drive to spin, rather than just the left side. So three programmers set out to prove it wasn't a coding issue: two lifted the robot off the ground while one moved the left joystick forward and back. Sure enough, only the left side moved. They then said, "see? mechanical problem," put the robot down, and went back to work.

Although I remember the time on 339 when a Victor burst into flames. All of the programmers (myself included) turned to the lead mechanical mentor and said, with confidence, "hardware problem!" It was rather funny at the time.

EDIT - Oh, and I saw this once:
Me: "The left motor needs to be reversed, but other than that, everything works well."
Electrical: "We can fix that in hardware!"
Programming: "We can fix that in software!"

<five minutes later>

Me: "Umm...the left motor is still reversed."
Electrical: "We fixed that!"
Programming: "We fixed that!"
Me: <facepalm>