|
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."
|
|
|
|
|
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
|
|
|
|
|
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.)
|
|
|
|
|
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.
|
|
|
|
|
I think you acted as a professional. Give the correct advice and argument, but if they really insist you have to do what they ask. Just make sure you always have "prove" of your said advice.
Not often, but on occasion I write emails in the line of: "I strongly advise against said feature, but I will implement as requested."
|
|
|
|
|
When someone demands stupid crap from me (and is as susceptible to logical reasoning, and reality for that matter, as Donald Trump), I usually do it, but keep proof of be being ordered to do that crap so I can shift the blame, when it arises, to the actual culprit. That's IMHO the best way.
|
|
|
|
|
I have run into this situation many times in a very long career.
This is typical of incompetent, technical management, which has been the bane of the industry since its inception.
The solution is to do as you have already done; keep copious notes of what you proposed and what you were told to do. Also ensure that all your notes are timestamped as to when you did what and when you were tasked with the assignments to override your proposals.
When you run into a personnel issue as you did, you will have your notes available for your defense.
I have fought many bad managers in my time and caused a lot of harm to their positions as a result (I got some fired.). However, unless you are willing to suffer the consequences (and there will always be consequences in business), do not take such an issue further than it has to go (ie: Your supervisor's boss, HR or Personnel).
If you believe that your defense of your actions is falling on deaf ears, look for another employer or assignment, since the situation will only occur again at some later time.
Me... I am hard-wired to fight bad or tyrannical authority. As a result, I spent a lot of time in my career defending others and defeating the stupidity and arrogance of technical management. Unfortunately, they are like bad politicians. Once you get rid of one bad apple another rotten one pops up.
It is a thankless fight but if more professionals were to respond rebelliously than such management may be more wary about going up against credible alternatives provided by their professionals...
Steve Naidamast
Sr. Software Engineer
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com
|
|
|
|
|
gjp1311 wrote: Was I really guilt in all of this? Should I have just ignored thier orders and didn't finish the task?
No. You did exactly as you should have done here -- you warned them, you kept records, you showed the records when they tried to blame you for their mistake.
Next time it happens, do all that again, but also talk to your boss before you perform the task that's going to break things.
|
|
|
|
|
Are low resolution swine pigselated?
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I bacon you Griff, stie away!
... such stuff as dreams are made on
|
|
|
|
|
No Sir Griff, they certainly are not. Oink an say that much.
... such stuff as dreams are made on
|
|
|
|
|
I could not have porcine that one coming.
"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
|
|
|
|
|
What ham could it cause? In my readings, I sausage advice porking fun at punsters
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
True. Some puns are larder than life.
... such stuff as dreams are made on
|
|
|
|
|
So, we're back bacon jokes about the fat again?
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I sure he a grease with you.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
It seemed like a great idea at the time. But in rindsight I am not so sure.
... such stuff as dreams are made on
|
|
|
|
|
This is getting a little rough around the edges Griff.
And would pigsellated swine be edible to VGAns?
I'm pretty sure I would not like to live in a world in which I would never be offended.
I am absolutely certain I don't want to live in a world in which you would never be offended.
Freedom doesn't mean the absence of things you don't like.
Dave
|
|
|
|
|
Bacon!
Everyone has a photographic memory; some just don't have film. Steven Wright
|
|
|
|
|
From the cybersecurity training:
Nonpublic information should only be saved to your network drive
Why do we even have hard drives then on our computers? IMO, non-public information includes source code, proprietary in-house and third party documentation, and so forth. WTF?
But this one:
The information on your computer is only fully protected by encryption when it is powered off or in hibernate mode. Simply locking your computer is not sufficient for encryption.
 Yeah, information is definitely "protected" when the computer is off. But how encryption protects your data when the computer is off is beyond me. Maybe I'm not as smart as I thought.
And unrelated, when I browsed over to norsecorp.com (live feed of cyberattacks, yeah, right) I got this (my bold):
This page is currently offline. However, because the site uses Cloudflare's Always Online™ technology you can continue to surf a snapshot of the site. We will keep checking in the background and, as soon as the site comes back, you will automatically be served the live version.
Dude. You really don't want to use "currently offline" and "Always Online" in the same sentence.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
