![]() |
Re: why blame the programmers??
The one I always find happens with me, is the robot code works flawlessly for 4 or 5 matches, then spontaneously STOPS working properly. I get told to check the code, and my response is invariably "code doesn't change on its own, if it worked before, then one of its inputs has changed, or ceased functioning" Its often that an encoder has died, or something along those lines.
|
Re: why blame the programmers??
Quote:
Defensive coding and stellar debugging skills will prevent wasting years of your career in the finger pointing game and will make you quite valuable to boot. |
Re: why blame the programmers??
Quote:
|
Re: why blame the programmers??
Quote:
|
Re: why blame the programmers??
It's not aways their fault and most of the time it's not.
|
Re: why blame the programmers??
Why? Because as part of the mechanical team, we can't possibly blame ourselves.
|
Re: why blame the programmers??
Ohhh I was dreading the comeback of this thread!
I've come to the conclusion, it's the age old story, and every team has it, and no-one will ever win it. But I will admit, as a programmer, we mostly do the bidding of the Design and Mech Teams. I think outside of the Control Board and Autonomous, we have no creative control. One day the code will be written first, and then a robot built around it :P |
Re: why blame the programmers??
Quote:
|
Re: why blame the programmers??
Quote:
Code:
void myfunction (void)Thus, the programmer's aren't blamed more often, they just have to do more work to find the problem before thy can even begin to fix it, thus it seems like they are always getting asked to fix things, since they are always working. |
Re: why blame the programmers??
Honestly, it only takes one integer or one symbol to make your robot go hay wire. But that only takes a second to fix. If it is mechanical failure, it is harder to fix. So people are being optimistic and blaming the one that is easier to fix. That is what I have learned from my experiences in the club.
|
Re: why blame the programmers??
People blame what they don't understand.
-Mechanical..although it takes time to master it, most people understand at least the very basics. -Electrical..a little more mysterious, but still, most people have some basic grasp. -Software..people seem to either get it, or think of it as black-magic that goes on deep within the cRIO. -As can be seen through the Salem witch trials and other historical examples, people like to take the easy way out and blame black magic for their problems :p |
Re: why blame the programmers??
you don't. it's not their fault. it's mechanical's fault.
|
Re: why blame the programmers??
The programers usually get blamed for several reasons:
I remember on specific instance during breakaway that our ball magnet was causing balls to be sucked under the robot. When the drive asked me how to stop the motor on the ball magnet (I was the spotter) I quickly told him to toggle the left throttle and hold buttons 4, 5, 6, and 12 for at least one second. It made sense to me at the time I programed it! |
Re: why blame the programmers??
Quote:
|
Re: why blame the programmers??
Over here we like to keep trying to improve our code. It sometimes involved changing what button did what.
An alumni last year placed a spray painted plate of aluminum on the driver station and had scratched in an operations manual. One of its directions was to ask programmers how we had set up the controls this time. This year we should have enough programmers so there will always be someone available to explain to someone else on the team what we did. Those mechanical guys blaming programming, they are just playing hard to get. They know they love how we type in stuff and then stuff happens, or break. |
| All times are GMT -5. The time now is 13:36. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi