|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: why blame the programmers??
but seriously, why not blame the programmers?
|
|
#2
|
||||
|
||||
|
Re: why blame the programmers??
But seriously, why should you? If you're trying to blame someone else for something, you should have a good reason for it.
|
|
#3
|
||||
|
||||
|
Re: why blame the programmers??
Hah our programmers always take the heat because they're stubborn. They'd rather run the risk of messing everything up by completely tearing down and rebuilding the program instead of switching two air tubes. They wait until the robot is completely built to start programing an autonomous. And they change and load the code without telling anyone. As mechanical, electrical, and driver I think they deserve all the blame they get.
|
|
#4
|
|||||
|
|||||
|
Re: why blame the programmers??
As electrical, it's your wires that pull out/mysteriously swap places, causing the code to go bad.
As a driver, you're the most hated person by the programmers. You tell them that the robot is broken, and it's a code problem (when a hard defensive maneuver took out a wire, say). As a mechanical, you failed to design and build the robot to the code that the programmers had put together. Because of all these, the programmers will say it's your fault. ![]() Now, why blame the programmers? They're sitting right there, that's why! Everyone else is moving around trying to fix the robot. ![]() |
|
#5
|
||||
|
||||
|
Re: why blame the programmers??
This happened during the last few hours of the build I have 1 limit switch programmed to stop one motor simple enough.
when the limit switch is tripped every thing just dies cant move any thing just dies WITH OUT MISSING A BEAT A MENTOR SAYS "Its the programming." and i explain the code in simplest terms so that a first grader would under stand it and with a dead serious face he still blames the programming. and what is worse is that we did not manage to fix the mechanical/wiring error. ![]() |
|
#6
|
||||
|
||||
|
Re: why blame the programmers??
Quote:
But thats only happened twice all of build season, once when a spacer for the lift was over-tightened, and again when a key fell out of a drive shaft. I think it's easiest to place blame on programmers because they sit and do work, moving a mouse never looks as accomplishing as welding or milling parts, but is just as significant to the success of the team. It still all their fault ![]() |
|
#7
|
||||
|
||||
|
Re: why blame the programmers??
If all else fails, blame the business team.
![]() |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Improving the experience of programmers and the effectiveness of code | kamocat | Programming | 18 | 25-12-2009 08:33 |
| Placing Blame | ExarKun666 | Chit-Chat | 17 | 24-04-2008 18:24 |
| Who to blame for the creation of the Trackball. | Chuck Glick | General Forum | 7 | 12-01-2008 22:35 |
| I blame robotics for... | JBotAlan | Games/Trivia | 12 | 05-12-2007 00:30 |
| blame it on the doggy robot | Andrew Rudolph | Chit-Chat | 0 | 26-10-2003 13:02 |