|
Or lighting up  with more people trying their hand at the 20 min Arduino Binary Counter challenge. And some of our members are participating in more than 1 challenge - we love that enthusiasm!
Congrats to our spot prize winner of the day - Florian. We hope you enjoy your new Arduino starter kit!
|
|
|
|
|
Does Captain Obvious shave with Occam's Razor?
|
|
|
|
|
|
If he shaves and if he has Occam's Razor and if it's sharp enough...
|
|
|
|
|
Yes, and he buys new blades with common cents.
|
|
|
|
|
|
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.
|
|
|
|
|
Yeah but such requests should pass the scrum-master, regardless of location.
... such stuff as dreams are made on
|
|
|
|
|
It sounds like you did your job and warned them of the consequences like a professional should. They are the managers and should be practiced with risk management. They made the mistake and are the accountable ones, not you; you did things correctly.
|
|
|
|
|
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 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 
|
|
|
|
|
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
|
|
|
|
|
Yeah. I had one boss that I had to do this with all the time for everything he ever told me!
He hated it but couldn't actually complain.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
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" 
|
|
|
|
|
That's going to be my new MO 
|
|
|
|
|
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. 
|
|
|
|
|
Slacker007 wrote: New job. No retarded software engineers.
I wouldn't put money on that. 
|
|
|
|
|
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. 
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Why does getting a new job mean it has to be another sweatshop, or that it will be a sweatshop. If people keep looking - like actually don't stop looking, you will find the right place and the right colleagues. It can be done.
|
|
|
|
|
35+ years in...had one perfect job. before an ill-advised takeover (via LBO) drove the company to bankruptcy...still looking. My advice is an old saying...don't let the perfect be the enemy of the good.
That said, if the job is truly miserable (and not simply inconvenient) then find a new one. The worst you can do is be miserable in new surroundings. At least its a change, huh?
|
|
|
|
|
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
|
|
|
|
|
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.
|
|
|
|
|
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."
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
