Live data from Hacker News

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

web.mit.edu

141–150 of 274 posts

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

#141
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 believe it's a problem in most industries and even humanity in general. I don't believe it's a business problem at all.

Heroes are lauded even if they solve problems they themselves are the cause of - which is conveniently either forgotten or denied - or they are solving non-issues that are deemed important by the ignorami-class. Politics, for example, is utterly dominated by this dynamic.

It's the first instinct: let the expert run the show. However, one of the (many) ways to let a complex project fall apart completely is to hand over full control to engineers. I'm one myself, but I know what I'm good at and what not. Dunning-Kruger is often mentioned in these discussions, but don't forget it also applies to engineers that often lack any management or leadership experience of any appreciable kind. They vastly overestimate their ability to handle management and organization-wide issues and tend to not only miss the forest for the trees but actually miss the trees for the leaves.

"Unix: A History and a Memoir" by Brian Kernighan actually mentions how proper management was crucial to their success. It's a detail that's frequently conveniently forgotten by the engineers who think themselves better than the "suits". For the record, I don't claim engineers are the primary problem, but it's not just management's either. Quotes like "who holds the company standing" and "who understands how to double click" are enormous smells and IMO make quite clear what's happening here.

I don't have ready-made solutions unfortunately, but I do wish we would look further than "it's the suits". It's a systemic, human problem that I believe is a natural result of operating under informational constraints and, very human, cognitive biases on all sides.

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

#142

Earlier quoted context omitted.

You define "productivity" as coding. The business defines it as "meetings, presentations, support, coding, whatever". Your productivity remains at 100% when you are doing what they want. I get that you thought you were hired as a coder, and thus measure your productivity by that. That's what I thought too. I ended up doing a lot of support (which is good, but that's another thread). Until I recalibrated my definition…

When did I say I code? I have been on the industry for 35 years. I have seen my share of technology evolutions and o have seen the work from a dozen different dimensions. If after all that time, I find the process painful, just trust me -- they can't change me, and I can't change them. You take the warts with the wins and move on. 2-3 bad weeks, 10 good weeks. Life moves on to next quarter. Complete CEO mindset :)

You heavily implied presentation preparation implies zero productivity. He tried to say this prep is also productive even if you personally don't or can't appreciate it.

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

#143
I remember finding a comment in the first codebase I ever worked on professionally in my first ever job.

It read "This fixes a bug that hasn't happened yet".

It seemed really smart at first, but later I learned that the developer that added that code also had a pattern of appending spaces to the start and end of user input and comparing the length to 2 to determine whether the value was empty or not...

So I'm fairly sure "that hasn't happened yet" was probably more a case of "that I personally haven't introduced unnecessarily yet" :)

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

#144
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

One of those days, however, you come up with another of your elegant, simple solutions and it actually replaces a 150K LoC monstrosity with either a 1K script or, even better, with nothing as a simple shift in perspective or process obsoletes it completely.

In the long run, IME, you'll be recognized either by management or your peers if you keep doing that over and over again.

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

#145

Earlier quoted context omitted.

"Je n'ai fait celle-ci plus longue que parce que je n'ai pas eu le loisir de la faire plus courte." ("I have made this longer than usual, only because I have not had the time to make it shorter.") Blaise Pascal

"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." — Antoine de Saint-Exupéry

"A facility for quotation covers the absence of original thought."

― Dorothy Sayers

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

#146
This is especially nice in the age of AI. I (the graybeard senior developer) does all the risky refactoring. I can take a performance issue and turn it into six regressions in half a day ($100). Then everyone is impressed when I let Opus fix these regressions in 20 minutes and $2 worth of AI.

No one notices when you cut 20% of some expensive process but cause no regressions.

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

#147
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 believe it's a problem in most industries and even humanity in general. I don't believe it's a business problem at all. Heroes are lauded even if they solve problems they themselves are the cause of - which is conveniently either forgotten or denied - or they are solving non-issues that are deemed important by the ignorami-class. Politics, for example, is utterly dominated by this dynamic. It's the first instinct:…

Bell Labs is an outlier in basically every aspect. Mr Kernighan lists stability of the environment with regard to funding, structure, mission as well as technical competence of the management as main drivers of the culture. This is just not the reality in companies that look for financial results on a quarterly basis and where the executives are MBA types.

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

#148
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 guess the point of view is that if a department is well running, it means it is overressourced. So you reduce the ressources until it's breaking point, just enough for it to not fail. A jaded service manager told me it was part of its official training: if the clients was too satisfied that meant that human ressources were wasted on them, so he had to spin plates between clients. I guess it was economically optimal.

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

#149
post #140

Earlier quoted context omitted.

Honestly? I’m just super direct with the exec team now after trying to do this dance. Obviously this is not allowed at every company, I’m just lucky to be at a place where the company culture allows for this. I’ll ask for something preventative or that otherwise hardens our systems. They ask “is it a need ?” and I’ll say something like “we can function without, but that means we have a 5-10% chance in the next 6mo of…

An example that not all companies are run by idiots. The job market is not a healthy market though, where its more important to know ppl then to be great at some skill. But if leadership sucks just leave if you can, that will fix the problem.

Totally. I am pretty lucky to be where I’m at.
Post reply on HN