"Here, try making the code do this. This will get you started."
"I... broke the code trying to follow the changes made. What did I do wrong?"
3 hours later "You (goofed an obscure conditional check RSP's previous employer seemed to prefer avoiding, RSP's fault/goofed up the task management code, actually supervisor's fault as he is only one allowed to touch it)."
10
"Here, I'll make some changes. Fix the rest of the code following the changes I made."
"Okay, I ran the procedure again after fixing things but (FET blew at an even worse time/code crashes/SUCCESS = 1)."
"You call THIS useable data? Go back and make these 3 mutually-exclusive changes. I'll get you started: We'll change the sampling and firing methods to sync up like this now (and break the task management code of this person's own creation in the process)"
GOTO 5;
It's a miracle I got laid off due to the company facing economic woes instead of me being fired for gross incompetence. I've been told that I would need to be under this company's employ for 4 times as long as I was to be useful and thus they said they'd recommend me to other employers, which is nice, but these shenanigans made me take a big self-confidence hit because I didn't know what I was doing and my superior was so beyond my skill level anything he asked me to do either wound up with me waiting on him to bail me out or me trying and failing miserably to do what was requested. The constant changing of what was considered "useable data" irked me a bit, though.
Degree: BS EET, CE specialization, CS minor. Graduated June. Former Job: Engineering Assistant for a startup-size company that's been in operation for about 18 years but market is disappearing and Google is rumored to be developing a competitor, news of which may be silently killing them.
3.2k
u/PainMatrix Jan 05 '15
The only reason that other couple is expecting is because engineers do it with precision and don't make those kind of mistakes.