Live data from Hacker News

Nobody ever gets credit for fixing problems that never happened (2001) [pdf]

web.mit.edu

161–170 of 274 posts

Re: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]

#162

I feel obliged to point out Stanslav Petrov, who absolutely got credit for fixing a problem that never happened. Granted it's a very extreme case.

Credit only in fame.

https://en.wikipedia.org/wiki/Stanislav_Petrov#Aftermath

> Petrov underwent intense questioning by his superiors about his judgment. Initially, he was praised for his decision.[2] Colonel-general Yuri Votintsev, the then-commander of the Soviet Air Defense's Missile Defense Units, who was the first to hear Petrov's report of the incident (and the first to reveal it to the public in the 1990s), states that Petrov's "correct actions" were "duly noted".[2] Petrov himself states he was initially praised by Votintsev and promised a reward,[2][22] but recalls that he was also reprimanded for improper filing of paperwork because he had not described the incident in the war diary.[22][23]

> Petrov has said that he was neither rewarded nor punished for his actions.[24] According to Petrov, he received no reward because the incident and other bugs found in the missile detection system embarrassed his superiors and the scientists who were responsible for it, so that if he had been officially rewarded, they would have had to be punished.[2][24][22][23] He was reassigned to a less sensitive post,[23] took early retirement (although he emphasized that he was not "forced out" of the army),[22] and suffered a nervous breakdown.[23]

Re: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]

#163
post #53

Earlier quoted context omitted.

I think a good place to start is tracking all the proactive things being done and reporting them. At least then maybe someone will see why it’s quiet, because you’ve anticipated the problems and stopped them before they start. When things come up with other teams, you’ll have a catalog of tasks that were done to show why you didn’t have the same issue. The work was done, just at a better time to avoid downtime.

> start is tracking all the proactive things being done and reporting them Speaking from experience, this does nothing. If you're at a company that is okay with average performers, then absolutely, 100%, fix all the bugs in advance, make the system rock solid and stable, prevent downtime, be a good engineer. If on the other hand if you're at a company where 10% of people must get stack ranked and PIP, or at a company…

> They set the rules of the game, you just play the game.

Obviously the only winning move here is not to play. Things like stack ranking are a perversion and no amount of compensation would be worth working for a company like that. If you choose to play, you're complicit in the moral abomination.

Re: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]

#164
post #17

I've been in those companies where "struggling departments" ended up getting all the praises and raise in budgets the following quarter because of the heroic saves they did, and raising awareness on how important they are... For stuff they totally caused on themselves. Meanwhile, my perfectly purring department was struggling to keep the lights on. It's a serious problem in this industry due to the disconnect between…

In my 35+ years in IT, the "hero attitude" was the one in the top three I most hated traits in a person working with or for me. And talking about traits, I considered crucial to always have in my teams a "saboteur" engineer - the one who thoght, found, come up with all the way we could break a design, service, infra components, app, etc., when all the others were designing or operating for perfect or normal conditions.

Re: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]

#165
post #157
post #17

I've been in those companies where "struggling departments" ended up getting all the praises and raise in budgets the following quarter because of the heroic saves they did, and raising awareness on how important they are... For stuff they totally caused on themselves. Meanwhile, my perfectly purring department was struggling to keep the lights on. It's a serious problem in this industry due to the disconnect between…

> I'm not sure how we solve this, other than having management come from engineering. I disagree with the implied idea here that "engineers are better managers". The solution is to have good management, not to assume that "engineers are better managers". I have seen good and bad managers, and in both groups there were engineers and non-engineers.

Engineers may not be better managers but it's not easy to really manage something you don't have any insight in.

Re: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]

#166
post #17

I've been in those companies where "struggling departments" ended up getting all the praises and raise in budgets the following quarter because of the heroic saves they did, and raising awareness on how important they are... For stuff they totally caused on themselves. Meanwhile, my perfectly purring department was struggling to keep the lights on. It's a serious problem in this industry due to the disconnect between…

Econometricians can solve it, bc we can create rigorous models that map causal inputs to output.

It’s extremely advanced technology, though, and most CEOs would rather rent seek / camp than give up some decision-making power (and very few are even aware it’s possible).

Re: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]

#167
post #17

I've been in those companies where "struggling departments" ended up getting all the praises and raise in budgets the following quarter because of the heroic saves they did, and raising awareness on how important they are... For stuff they totally caused on themselves. Meanwhile, my perfectly purring department was struggling to keep the lights on. It's a serious problem in this industry due to the disconnect between…

Econometricians can solve it, bc we can create rigorous models that map causal inputs to output. It’s extremely advanced technology, though, and most CEOs would rather rent seek / camp than give up some decision-making power (and very few are even aware it’s possible).

Do you have any good sources for this I'd be interested in learning more

Re: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]

#168
post #17

I've been in those companies where "struggling departments" ended up getting all the praises and raise in budgets the following quarter because of the heroic saves they did, and raising awareness on how important they are... For stuff they totally caused on themselves. Meanwhile, my perfectly purring department was struggling to keep the lights on. It's a serious problem in this industry due to the disconnect between…

could an AI product solve this?

Re: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]

#169
post #17

I've been in those companies where "struggling departments" ended up getting all the praises and raise in budgets the following quarter because of the heroic saves they did, and raising awareness on how important they are... For stuff they totally caused on themselves. Meanwhile, my perfectly purring department was struggling to keep the lights on. It's a serious problem in this industry due to the disconnect between…

itemize the problems you are preventing

"Accounted for X situation" "Added gaurdrails to protect against Y"

When working as a business analyst i have to do this sort of thing all hte time or else id get no credit for half my work

Re: Nobody ever gets credit for fixing problems that never happened (2001) [pdf]

#170
post #9

There are a lot of things like this. My favorite is how elegant solutions often look simple in retrospect. So if you noodle on a problem for a while and then come up with a clever solution: once you explain it to someone they'll be like, "yeah, of course." Meanwhile the guy next to you that overcomplicates the problem ends up getting kudos for building something so difficult :D

"An idiot admires complexity, a genius admires simplicity"
Post reply on HN