Live data from Hacker News

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

web.mit.edu

271–274 of 274 posts

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

#271
post #86

Earlier quoted context omitted.

I'm curious why things would have shut down when the system thought it was 1900. What part of the logic had the effect of "shut the system down if current date is less than (X date)?" (If you can remember the code 25+ years later, that is).

I only worked with the team making changes to the billing system (and even then, I only maintained a database of code modules, who worked on them, and what changes had been made - this was before git and we did version control painfully). As you can imagine, the billing system was definitely not going to survive the date suddenly being 99 years older than it was last month. So I don't really know why the rest of the…

> So when they say that it would all have stopped if the work wasn't done, I believe them ;)

Fair enough, they were certainly in a position to know, and their willingness to spend oodles of money on it proved that they believed it.

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

#272
post #257

Earlier quoted context omitted.

IT doesnt control the funding so at that point its not an issue of awareness but a management decision to live with this problem and focus funding elsewhere more often than not, many things in the business are on fire and underfunded at the same time. you can get recognition for your work without the problem being permanently solved the right way, and it may not result in more funding but peopel will think of you for…

It comes back to communication. If management acknowledges the issue but redirects budget elsewhere due to priorities, it's legit. Communicating it in a way IT personnel understand and accept isn't necessarily easy. Sometimes there's also incentive for management to avoid it altogether (we need to focus elsewhere and this could burn you out, but you're an acceptable loss). That said, management needs to know there's…

> That said, management needs to know there's pain and in a language it speaks - risk. Cost, legal, whatever.

In my own experience, people in management generally refuse to evaluate risks that are not immediate. Instead of looking at risks as something that could happen the general mode is looking at risks as something that may not necessarily happen and therefore does not need immediate attention.

Raising risks becomes a risky business (pun intended, hehe). If you raise, especially repeatedly, that in x weeks/month something will probably happen a manager will sweep that under a rug, ignore any warnings and will not give (even more so fight for) resources to proactively tackle the risk. Yet, if the risks manifests and hurts business metrics, then suddenly you are remembered and get all the blame. Yet, if you wait it out and clean up the mess caused by the risky event, you are a hero.

The higher up the management chain one is, the more prevalent this phenomenon is. I don't want to imply there's no planning or that management types are "dumb" or whatever. It's just that in my experience, the higher up one is, the more they are focused on the proverbial happy path. It's generally easier to get a goalpost moved instead of getting a blocker risk removed. All the projects that exceed budgets and underdeliver are, in part, a symptom of this: raising a simple "we don't have safeguards against a third party in a critical path delivering in time and under budget" project risk makes someone look bad and is generally unacceptable, yet once the deadline is up getting more budget assigned is one meeting away. I'm always surprised how strong a simple moat of simply already being in the market can be: businesses that continuously take all-or-nothing type of risks keep surviving against simple mathematical odds.

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

#273

Earlier quoted context omitted.

If I move out a bit of my circle, where people do all kinds of work, I'd say that there's generally a stigma on the "IT" workers. Moreover the stigma is there even within the IT company/industry itself, where sales, marketing, non-engineering parts of management, and other similar types of supporting roles also look down on the engineering. And this unfortunately includes family members too. I learned that people are…

I do think of all my computer work as predominantly janitorial.

Sure there are such examples I guess.

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

#274
post #174
post #159

Earlier quoted context omitted.

Dunning Kruger's paper didn't even show the Dunning Kruger effect everyone loves.

In the original DK experiment they asked students after they had taken a test that where would their score end up compared to their classmates (which they had no knowledge of). Obviously they picked scores around the middle* Which resulted in top students 'undervaluating themselves' and bottom students 'overestimating themselves'. Or under/overvaluating a random future variable that they don't have knowledge of, at l…

Thanks for elaborating!
Post reply on HN