Experienced Co-workers (Enzineers)

[Casawi]

Here is what ticks me the most:

- Never convinced the problem is on their end, and always will make a case how it is on someone else end (me).
- Cannot convince them there is a bug, I must have proof .. or else i am just running my mouth until crunch time and... the bug comes back to hunt us.
- Always find a good reason why the bug was there in first place... its never ... yeah I should have done it differently.
- When a bug is reported and everyone in the group is CC'ed on it, I only get a reply... no one else can keep track of the crap.

Anyone else have some issues with experienced engineers ?

Sorry if the post is boring, I need a break.

 

[Chaotic42]

It's not just engineers. Office jobs are a constant war against the stupid and the lazy. Always CC everyone who needs to read your emails. Respond to these direct emails with "Okay", but CC everyone who should be on there. Don't get sucked into that.

If you should have done something differently then a new ISO procedure needs to be written immediately.

Requiring proof of bugs makes sense.

 

[spidey07]

They act that way because they've seen it hundreds of times and most of the times the trouble is on your end.

 

[JohnCU]

stop hatin

 

[Casawi]

Originally posted by: Chaotic42
It's not just engineers. Office jobs are a constant war against the stupid and the lazy. Always CC everyone who needs to read your emails. Respond to these direct emails with "Okay", but CC everyone who should be on there. Don't get sucked into that.

If you should have done something differently then a new ISO procedure needs to be written immediately.

Requiring proof of bugs makes sense.

Sometimes... the bug happens randomly when I am not looking for it. To track the proof down, I would have to drop what I am doing.... but yeah it nice to have proof, but I think they should at least thinking about what I described and how it can be a problem.

 

[Casawi]

Originally posted by: JohnCU
stop hatin

I am not hating... I really like the guy, he is sharp... but I am going to have to work all weekend, while my gf is visiting, because we ignored these things. I have to make sure his changes don't screw up my work ... you know how that goes.

 

[Chaotic42]

Originally posted by: Casawi
Sometimes... the bug happens randomly when I am not looking for it. To track the proof down, I would have to drop what I am doing.... but yeah it nice to have proof, but I think they should at least thinking about what I described and how it can be a problem.

Ideally, yes, but remember that they probably feel about like you do. They get a lot of people complaining about bugs that don't exist and probably very little praise when everything works properly.

Take the time to document the bug. Not to sound like some HR representative, but quality is everyone's responsibility. Believe me, I've been through enough product deliveries to know that things like ISO and 6 Sigma aren't just jokes to make you miserable.

 

[Casawi]

Originally posted by: Chaotic42

Originally posted by: Casawi
Sometimes... the bug happens randomly when I am not looking for it. To track the proof down, I would have to drop what I am doing.... but yeah it nice to have proof, but I think they should at least thinking about what I described and how it can be a problem.

Ideally, yes, but remember that they probably feel about like you do. They get a lot of people complaining about bugs that don't exist and probably very little praise when everything works properly.

Take the time to document the bug. Not to sound like some HR representative, but quality is everyone's responsibility. Believe me, I've been through enough product deliveries to know that things like ISO and 6 Sigma aren't just jokes to make you miserable.

Certainly documentation ... I learned that the hard way. You know a few times I sent redundant emails, just so there is a proof ... came in sooo handy... I left the meeting, and grabbed my laptop to read the email to everyone. NO MORE DISCUSSION after that...lol.