Developers are always the problem. Or are they?
-
I recently had a problem at my job. We work for a company abroad as contractor, so all our communication is done by Slack and our tasks are on TFS. The task I want to talk about, was basically to hardcode some items in a list that came from a database. I warned them all that this would break some other modules in our application, because it used that same data. They just told me to finish that task and go on. It didn't work out and it broke the application, as I have told them many times before. But my main complaint is that, they sent an email to my manager saying that the RC was broken because of me. I did have all chat history, so it was easy to prove to my boss that I just did what I was told and even warned them many times about that. Was I really guilt in all of this? Should I have just ignored thier orders and didn't finish the task?
-
I recently had a problem at my job. We work for a company abroad as contractor, so all our communication is done by Slack and our tasks are on TFS. The task I want to talk about, was basically to hardcode some items in a list that came from a database. I warned them all that this would break some other modules in our application, because it used that same data. They just told me to finish that task and go on. It didn't work out and it broke the application, as I have told them many times before. But my main complaint is that, they sent an email to my manager saying that the RC was broken because of me. I did have all chat history, so it was easy to prove to my boss that I just did what I was told and even warned them many times about that. Was I really guilt in all of this? Should I have just ignored thier orders and didn't finish the task?
-
You did the right thing. But the next time this happens you should find somebody on "your side" to insist on your line. But maybe that function is missing from your organisation :|
... such stuff as dreams are made on
-
Yeah, basically all my co-workers are on another country, including the scrum master and pm. My boss here just deal with things like contracts, hiring and etc.
-
I recently had a problem at my job. We work for a company abroad as contractor, so all our communication is done by Slack and our tasks are on TFS. The task I want to talk about, was basically to hardcode some items in a list that came from a database. I warned them all that this would break some other modules in our application, because it used that same data. They just told me to finish that task and go on. It didn't work out and it broke the application, as I have told them many times before. But my main complaint is that, they sent an email to my manager saying that the RC was broken because of me. I did have all chat history, so it was easy to prove to my boss that I just did what I was told and even warned them many times about that. Was I really guilt in all of this? Should I have just ignored thier orders and didn't finish the task?
-
I recently had a problem at my job. We work for a company abroad as contractor, so all our communication is done by Slack and our tasks are on TFS. The task I want to talk about, was basically to hardcode some items in a list that came from a database. I warned them all that this would break some other modules in our application, because it used that same data. They just told me to finish that task and go on. It didn't work out and it broke the application, as I have told them many times before. But my main complaint is that, they sent an email to my manager saying that the RC was broken because of me. I did have all chat history, so it was easy to prove to my boss that I just did what I was told and even warned them many times about that. Was I really guilt in all of this? Should I have just ignored thier orders and didn't finish the task?
You did ok. Good to keep records. You could have gone to your manager and tell him the requested changes would break the application before doing them.
I'd rather be phishing!
-
I recently had a problem at my job. We work for a company abroad as contractor, so all our communication is done by Slack and our tasks are on TFS. The task I want to talk about, was basically to hardcode some items in a list that came from a database. I warned them all that this would break some other modules in our application, because it used that same data. They just told me to finish that task and go on. It didn't work out and it broke the application, as I have told them many times before. But my main complaint is that, they sent an email to my manager saying that the RC was broken because of me. I did have all chat history, so it was easy to prove to my boss that I just did what I was told and even warned them many times about that. Was I really guilt in all of this? Should I have just ignored thier orders and didn't finish the task?
I faced the same problem many times, it seems some managers deliberately only communicate verbally so they can just deny that they made a wrong request, sigh :sigh:
-
I recently had a problem at my job. We work for a company abroad as contractor, so all our communication is done by Slack and our tasks are on TFS. The task I want to talk about, was basically to hardcode some items in a list that came from a database. I warned them all that this would break some other modules in our application, because it used that same data. They just told me to finish that task and go on. It didn't work out and it broke the application, as I have told them many times before. But my main complaint is that, they sent an email to my manager saying that the RC was broken because of me. I did have all chat history, so it was easy to prove to my boss that I just did what I was told and even warned them many times about that. Was I really guilt in all of this? Should I have just ignored thier orders and didn't finish the task?
You did the right thing. Its nice to see someone who cares enough to struggle with the ethics of this all-to-common situation. I'm simply happy you still had the chat available. When I find myself in this situation, I usually send an e-mail to person I chatted with...something like "I enjoyed our recent discussion about BLAH. If I understood correctly, you would like me to do WHATEVER to BLAH? Since I had some concerns, could you please confirm that I have understood correctly? Thank you." I then CC anyone who is directly affected. This gives anyone who cares a chance to object and creates evidence that is hard to dispute. One of my old bosses jokingly called this "getting as many fingerprints as possible on the murder weapon" :)
-
I faced the same problem many times, it seems some managers deliberately only communicate verbally so they can just deny that they made a wrong request, sigh :sigh:
I've taken to always sending a follow up email recapping the conversation, it's better than nothing.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst "I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
-
You did the right thing. Its nice to see someone who cares enough to struggle with the ethics of this all-to-common situation. I'm simply happy you still had the chat available. When I find myself in this situation, I usually send an e-mail to person I chatted with...something like "I enjoyed our recent discussion about BLAH. If I understood correctly, you would like me to do WHATEVER to BLAH? Since I had some concerns, could you please confirm that I have understood correctly? Thank you." I then CC anyone who is directly affected. This gives anyone who cares a chance to object and creates evidence that is hard to dispute. One of my old bosses jokingly called this "getting as many fingerprints as possible on the murder weapon" :)
-
I recently had a problem at my job. We work for a company abroad as contractor, so all our communication is done by Slack and our tasks are on TFS. The task I want to talk about, was basically to hardcode some items in a list that came from a database. I warned them all that this would break some other modules in our application, because it used that same data. They just told me to finish that task and go on. It didn't work out and it broke the application, as I have told them many times before. But my main complaint is that, they sent an email to my manager saying that the RC was broken because of me. I did have all chat history, so it was easy to prove to my boss that I just did what I was told and even warned them many times about that. Was I really guilt in all of this? Should I have just ignored thier orders and didn't finish the task?
Listen, you obviously know you are working at the wrong company. Get a new job where the "other" software engineers are not retarded. Fresh chips and salsa. Ice cold raspberry seltzer. New job. No retarded software engineers. Good luck. :thumbsup:
-
I've taken to always sending a follow up email recapping the conversation, it's better than nothing.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst "I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
-
I recently had a problem at my job. We work for a company abroad as contractor, so all our communication is done by Slack and our tasks are on TFS. The task I want to talk about, was basically to hardcode some items in a list that came from a database. I warned them all that this would break some other modules in our application, because it used that same data. They just told me to finish that task and go on. It didn't work out and it broke the application, as I have told them many times before. But my main complaint is that, they sent an email to my manager saying that the RC was broken because of me. I did have all chat history, so it was easy to prove to my boss that I just did what I was told and even warned them many times about that. Was I really guilt in all of this? Should I have just ignored thier orders and didn't finish the task?
gjp1311 wrote:
Should I Should have just ignored thier orders and didn't finish the task
FTFY Seriously, I get the same thing here, and have learned to object to stupid things. If it's something that's likely to break other things (that I'll likely have to redo later...or worse get blamed for) I do it the right way the first time. That usually means 'pretending to understand' but doing what I want anyway. The fallout from overdoing something is a lot less than taking unnecessary and even dangerous shortcuts. The trick is to give them what they want without going into the details of how you actually got it done. All they should care about is that it works. (or is there more to loading a list from a database query that I should consider?...requires dba approval?...requires online connection?) :)
"Go forth into the source" - Neal Morse
-
I recently had a problem at my job. We work for a company abroad as contractor, so all our communication is done by Slack and our tasks are on TFS. The task I want to talk about, was basically to hardcode some items in a list that came from a database. I warned them all that this would break some other modules in our application, because it used that same data. They just told me to finish that task and go on. It didn't work out and it broke the application, as I have told them many times before. But my main complaint is that, they sent an email to my manager saying that the RC was broken because of me. I did have all chat history, so it was easy to prove to my boss that I just did what I was told and even warned them many times about that. Was I really guilt in all of this? Should I have just ignored thier orders and didn't finish the task?
Been there. Made some huge required changes and warned the users via a templated email that we always send for changes. Had a testing period that they signed off on. Goes to production and bam. Users were mad. Said we should have put it red and bolded it so they would have noticed it.
-
Been there. Made some huge required changes and warned the users via a templated email that we always send for changes. Had a testing period that they signed off on. Goes to production and bam. Users were mad. Said we should have put it red and bolded it so they would have noticed it.
-
I recently had a problem at my job. We work for a company abroad as contractor, so all our communication is done by Slack and our tasks are on TFS. The task I want to talk about, was basically to hardcode some items in a list that came from a database. I warned them all that this would break some other modules in our application, because it used that same data. They just told me to finish that task and go on. It didn't work out and it broke the application, as I have told them many times before. But my main complaint is that, they sent an email to my manager saying that the RC was broken because of me. I did have all chat history, so it was easy to prove to my boss that I just did what I was told and even warned them many times about that. Was I really guilt in all of this? Should I have just ignored thier orders and didn't finish the task?
This happens to all employees at some time or another. You did what was asked and can show it by the history of communications. Alas, that doesn't stop a manager from retaliating. In the end, you can't really protect yourself from a manager trying to protect themself, especially in a contract situation. (One thing I've done in similar situation is ensure that the change can be easily reversed and/or isolated, like wrapping the change in a macro or putting it in a separate module.)
-
The old "normally we ignore everything from you" gambit with the associated corollary that "even if you inform us and we ignore you it is still your fault."
I get that at home, dammed if I will put up with it at work.
Rick York wrote:
even if you inform us and we ignore you it is still your fault
Never underestimate the power of human stupidity RAH
-
I recently had a problem at my job. We work for a company abroad as contractor, so all our communication is done by Slack and our tasks are on TFS. The task I want to talk about, was basically to hardcode some items in a list that came from a database. I warned them all that this would break some other modules in our application, because it used that same data. They just told me to finish that task and go on. It didn't work out and it broke the application, as I have told them many times before. But my main complaint is that, they sent an email to my manager saying that the RC was broken because of me. I did have all chat history, so it was easy to prove to my boss that I just did what I was told and even warned them many times about that. Was I really guilt in all of this? Should I have just ignored thier orders and didn't finish the task?
I'm at the age where I simply don't do things that I know will cause harm. And it sounds like your team doesn't understand Scrum.
-
Listen, you obviously know you are working at the wrong company. Get a new job where the "other" software engineers are not retarded. Fresh chips and salsa. Ice cold raspberry seltzer. New job. No retarded software engineers. Good luck. :thumbsup:
Slacker007 wrote:
New job. No retarded software engineers.
I wouldn't put money on that. ;)
Latest Article - Building a Prototype Web-Based Diagramming Tool with SVG and Javascript Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
Listen, you obviously know you are working at the wrong company. Get a new job where the "other" software engineers are not retarded. Fresh chips and salsa. Ice cold raspberry seltzer. New job. No retarded software engineers. Good luck. :thumbsup:
Slacker007 wrote:
Get a new job where the "other" software engineers are not retarded.
It sounds like the OP is working for a "coding sweatshop", where the answer to almost any problem will be "shut up and write code". Moving to another "sweatshop" isn't going to change much, and the positions in good companies aren't that easy to get. :sigh:
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.