|
|
Corporations are no place to innovate. They are the place where rules such as 'if it works, don't touch it', and office politics apply. If you posses a creative personality then you should find yourself a company that appreciates it.
Or found one.
|
|
|
|
|
I'd react by looking for a new job.
|
|
|
|
|
|
I worked with a development manager like that once, we, the developers, would strategise how we could get him to take ownership of a new idea when we wanted it implemented. It worked rather well, if you wanted to kill an idea present it as your own, to get it through get him to present it as his idea.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I had a guy like that at my old job.
|
|
|
|
|
Vunic wrote: write about it and share it with your bosses/ directors. They , for sure not caring to read it fully, reply back with a standard "Great thoughts Bob!" type replies.
Problem is you write about it, directors aren't going to bother reading it, they just don't.
they need a picture, be it the idea, the use case, the financial incentive
Vunic wrote: They quote a "Flash news" of a competitor company and say, "What a beautiful, critical feature they've done & they are in the news".
Yes of course, because they saw this.
Show a director or other high level something, you've got maximum 10 seconds, probably less to make your case. A fancy written report will fail, every time.
show a picture if you can, if it's words use as few as possible, your idea has 10 (plan for 5) seconds to sell itself.
Installing Signature...
Do not switch off your computer.
|
|
|
|
|
It's as though you were talking about small children -"they need a picture", "show a picture", "...words uses as few as possible" etc
Oh I see my mistake...
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Join the competitors? At least they thought about the idea and implemented it.
And you'll find such "directors" in more places than I care to count.
I am not the one who knocks. I never knock.
In fact, I hate knocking.
|
|
|
|
|
Ever wonder how startups / new companies form? Most of the time Many times, it's pissed off former employees.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
Quote: And he simply admires heaping praises for the competitors "good job"
That must foster all sorts of warm fuzzy feelings in the company. 
"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
|
|
|
|
|
Vunic wrote: I was thinking if I should simply ignore it and keep going.
There are alternatives of course.
Don't make any more suggestions.
Find a different job.
Keep a record (email probably) of suggestions and specifically fire off copy to many people pointing out it was your idea way back when. This might seem petty but isn't if reviews look for this and raises/bonuses come from reviews.
Vunic wrote: I conveyed my frustrations clear. Now he's saying , "Mate, it's all a team work, why are you so specific in claiming a credit, you have to be magnanimous".
Given that I have never been in this specific situation and without knowing the exact specifics I cannot state for sure how I would react but I suspect it would involve quite a bit of anger.
I do know that when one lead started suggesting that I didn't know what I was doing based on his verbal instructions I specifically started requesting explicit instructions via email which I kept. That way I could demonstrate that I was following his instructions exactly as he stated.
|
|
|
|
|
Reading this morning, about the error that seems to have locked several hundred million dollars of Etherium crypto currency, I wonder how many CP members are allowed to poke around in live systems. To me it seems like wandering around a minefield with closed eyes.
We're philosophical about power outages here. A.C. come, A.C. go.
|
|
|
|
|
if you play with matches you get burnt!
|
|
|
|
|
MarcusCole092076 wrote: if you play with matches you get burnt!
Note to self: include 1 box of matches for each user and place 1 more to each workstation.
modified 13-Nov-17 9:47am.
|
|
|
|
|
It seems like every month in QA we get someone asking how to undo an SQL DELETE or UPDATE query where they forgot the WHERE clause and the production DB is well and truly screwed. And of course we have to tell 'em "go talk to you boss, now. Run, do not walk."
Sandbox, separated dev environment, whatever: if you are testing development code against a live system, you are an idiot, and will get burned.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
he shouldn't have access to the Prod environment to begin with.
|
|
|
|
|
Slacker007 wrote: he shouldn't have access to the Prod environment to begin with.
At my last job we had access to production and even did the code updates. Then we hired a networking nazi dude who took our access away. Slowed us way down.
At this job I have access to production. Sometimes it is necessary. I hate working places where they put barriers in place just because.
There are two kinds of people in the world: those who can extrapolate from incomplete data.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
I have been doing this for over 15 years, and have never had access to Prod. Didn't slow us down.
With that said, we had deployment engineers and sys admins that had access to Prod. Our DBAs had access to prod, but the engineers/developers did/do not.
I don't agree with your standing that you should have access to Prod. If you are fixing things in Prod then you guys are messing up somewhere else down the production line.
My two cents. 
Edit: also, if you have an issue in Prod that needs to be fixed, then you try to roll back at all costs. That is what a rollback plan is for. your deployment engineer should have one. 
|
|
|
|
|
Probably a difference between large and small companies perhaps.
There are two kinds of people in the world: those who can extrapolate from incomplete data.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
I don't even have access to the production domain, if I want to get the latest production data I need to go beg a favour from the project manger woh won't even fart unless he has been through the checklist for it.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Yet:
The price of Ethereum on Wednesday was up 2.3% to $301.25.
The irony of it all.
|
|
|
|
|
Herbie Mountjoy wrote: I wonder how many CP members are allowed to poke around in live systems.
I don't do it.
I refuse credentials and make a specific point of asking operations for data rather than access. If direct access is required then I do it in a pair set up with an operations person.
I also push that idea as part of the development process - developers should never have access.
I worked at one place where a casual question lead to be me finding out that the DBA was doing all of their development work on the production database and was not checking anything into source control. As I recall I don't even think they knew what source control was.
|
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Rose | [Rose]](https://www.codeproject.com/script/Forums/Images/rose.gif)