|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Do you get blamed for every thing one your team!!!
I am a programmer, of course I do.
|
|
#2
|
||||
|
||||
|
Re: Do you get blamed for every thing one your team!!!
Personally, we blame the programmers.
However, yesterday someone else took all the blame, after all it was their fault. Condensed story: Alignment on wheels was off, so I was holding onto the robot. Told the certain person to move the slider a little down, they put it all the way up. Robot dragged me across the room, into a wall, then the person over-compensated, and the robot reversed, pushing me the other way. It was an... interesting.... day. Needless to say that person was blamed for the rest of the day, especially when the chain ripped off, ripped through the plexiglass our electrical was mounted on, and broke one of the spikes that I was then forced to repair. ![]() |
|
#3
|
||||
|
||||
|
Quote:
|
|
#4
|
||||
|
||||
|
Re: Do you get blamed for every thing one your team!!!
mistakes (or the proper engineering term: bugs) is something you will deal with for the rest of your life if you are an engineer.
You have to develop a new way of thinking: 1. the only way you can completely avoid making any mistakes is to do nothing all the time. Unfortunately its hard to find someone to pay you money to do nothing. 2. When you are designing and fabricating a system, mistakes (bugs) are expected! This is why we have test equipment in the lab (lots of expensive test equipment), an acceptance test procedure that makes sure the system does everything it is suppose to do, and a manufacturing test procedure to make sure that each unit built is correctly fabricated and assembled. 3. Trying to create a design and assembly process in which no mistakes EVER make it out the door results in super-high quality AND super-high prices (think $900 AirForce Hammer) 4. when you are in the design phase you try to avoid mistakes (bugs), by having design reviews and checklists for each step of the project. 5. after you assemble a prototype you try to FIND mistakes (bugs) by testing testing and more testing. At this point bugs are golden because finding them keeps defective product from going out the door, and it lets you go back and see where the bug was introduced in the design of the product, so you dont keep making the same mistakes over and over. With all this said, the idea of making mistakes is very different to engineers than it is with most people. We dont attach our egos to our work. If we make a mistake its not because we are stupid, or not trying hard enough, or we dont know what we are doing its because we are engineers, and engineers venture into unknown territory BOLDLY, doing things no one has ever done before. BTW, a good example of this "new way of thinking" is what happens at design reviews. When we review another engineers work we NEVER say anything about the designer, only about the design. If you find a mistake you dont say "whoa, this is stupid, what were you thinking?" we say: this doesnt look right to me, I think you need something more like this......" Once you contribute something to a design or fabrication, its not 'you' anymore, its the design, its the system. Personal performance reviews are separate, held behind closed doors with your manager, not infront of all your co-workers. An even then, a good engineering manager will never say "you dont seem to know what you are doing", or "you do a lot of stupid things". Performance reviews say focused on the quality of your work, and things you can do (training, etc) to improve your performance. Last edited by KenWittlief : 21-01-2006 at 15:58. |
|
#5
|
||||
|
||||
|
I'm not a new guy, this is my second year but i am a programmer, so I get blamed for everything anyway.
Robert Flanagan, 1390, St. Cloud, Florida |
|
#6
|
|||
|
|||
|
Re: Do you get blamed for every thing one your team!!!
On my team the new programmers (ME!), along with the old programmers, get blamed for almost everything!
|
|
#7
|
||||
|
||||
|
Re: Do you get blamed for every thing one your team!!!
I got blamed for a lot of stuff my first year (last year) because everyone knew my older brother, and they didn't like him, so they decided they didn't lik me. But I fixed that as soon as possible by doing a lot of stuff right, when they thought i couldn't, so that's all you have to do, work hard, work right, and you should be fine.(although i'm still blamed a lot)
|
|
#8
|
|||||
|
|||||
|
Re: Do you get blamed for every thing one your team!!!
i get blamed for things that happen on the other side of the room all because of montclaire mayhem...
<goes into overly eleberate flash back> i remeber it like it was yesterday i was driving the robot in the finals and twice we were clipped and pulled down by a passing robot cough 1626 cough no hard feelings so the second time the manipulator arm was bent way to the side. <comes back to present> so anyways no everyone calls me the bender even rookies no one beleives me that it wasnt my fault only 4 members went to that event so i tell people that if they wanted anything diffrent to happen they should of been there my team inspired the nick under the name team scape goat |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| How do you organize your team? | NoodleKnight | Team Organization | 18 | 03-11-2005 22:57 |
| First Year Team Assistance - MOEmentum: FYI | Mr MOE | General Forum | 0 | 07-01-2005 14:07 |
| Kettering University Rookie Robotics Team | Alexander McGee | General Forum | 23 | 22-12-2004 09:13 |
| The 2003 Index of team's post about their robot... | Ken Leung | Robot Showcase | 4 | 28-02-2003 00:18 |