Live data from Hacker News

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

web.mit.edu

301–310 of 446 posts

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

#301
post #27

I've been contemplating the issue in the headline, as pertains to my value. When I help somebody in 40 mins with something they've been stuck on for 3 months, my value is clear to everyone. When I work there the whole time, and nobody ever gets stuck for 3 months, my value is unclear. Don't know how to deal with this paradox.

Life and its rewards aren't perfect. Work with honest, intelligent people; genuinely do your best; your days will be much better and the odds will be with you.

> Work with honest, intelligent people

I'll let you know when I find this communist utopia.

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

#302

Earlier quoted context omitted.

The trick is to do these sort of engagements as a fixed price contract. You could have probably done an assessment in a hour or two. Then you charge on what you estimate is the value to the company.

I should have, but it would have been obvious that I pulled a fast one on them as the fix was really quite simple. Instead of building a Hadoop cluster I replace a sql sub query with a bitmask. It really only took an hour to figure it out but they let me charge the whole day.

Ok, it doesn't sound that bad to me? You learned something about consulting, got paid 1600$ for one hour work, got good recommendations and now have time for another interesting opportunity.

Don't waste your time and clients money on pretending to do work that you don't. Its ethically wrong (maybe even criminal) and it sounds like you would be bored to death wasting your talent.

Don't blame the company for not wasting its money either. It did pay for the whole day and gave you good recommendations.

You could do fixed price. Or split the difference (on both sides of the estimate), which provides good incentives for both parties.

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

#303
post #274

Earlier quoted context omitted.

Totally get where you're coming from, but it's also kinda splitting hairs. Being reasonable is part of being intelligent. Surrounding yourself with intelligent people doesn't necessarily mean "surround yourself with the highest IQ individuals you can find." (not saying you're saying that explicitly, just that i think you're just using a definition of intelligence that's narrower than the parent) Working well with oth…

> Being reasonable is part of being intelligent Not in the slightest, those two are quite separate.

Well the parent made sort of a case for why being reasonable is part of being intelligent, and your response was to claim there was no correlation without an argument.

I happen to believe that reasonableness is part of being intelligent, by the following criteria:

1. when you are reasonable you do not make unreasonable demands that will just be troublesome and cause workflow issues because in the end they are unachievable.

2. a reasonable person will be able to determine what other people are capable of in given situations, and be able to structure things in such a way that other people can perform to best meet expectations.

3. the root of reasonable is reason, a reasonable person can be reasoned with because they possess the quality of reason, in most of the history of philosophy if you do not possess the ability to reason you are an idiot.

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

#304
post #272

Earlier quoted context omitted.

Or worse: People get stuck quite frequently and ask you for help pretty quickly. You get everyone unstuck, but your own work falls behind and when your boss's boss asks for metrics on developers you have few points delivered and few LOC changed. Your boss tries to explain, but your head is the one that rolls next when layoffs happen.

Great workers know when they can help others without falling behind themselves. Or have good communication skills to explain what they were doing.

Or are good at communicating and don't need to do anything because they can just lie.

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

#305

This is wonderful description of the kind of hellhole corporate Scrum is turning into. Agile was literally about doing things quickly and quick cycles of capability improvement. But Scrum is a worse version of the planning processes it meant to replace! If anything, the way scrum lays out the work into immediate problems exacerbates the cycle. In the long run it just turns into a ticketing system where fires get push…

Agile seems to have ended up as a way for PMs to report upward to senior managers who also need to report upward.

You can see why. These people have to decide what will be worked on out of all the potential things that can be worked on. Someone has to make that decision. Will this feature make us money? What about that bit of work that doesn't add a feature but reduces resource costs? What about tech debt that I'm told is building up and slowing the ability to deliver features?

I'm not a senior manager, but ultimately someone up the chain is responsible for the company surviving and making money and paying our salaries. They are just like you and I, trying to make decisions based on what little information that can glean. So part of that is "what will this cost and how much will it be worth" vs "what will that other thing cost and how much will it be worth".

To that end, they need some way to estimate this. They latched on to agile as it was being promoted by tech as a way to do this. Whose fault is that?

And so with that came all the frequent estimations, are we on track, rituals, etc. Some people don't believe this should naturally follow. I agree. But somehow all those rituals have become part of the cult.

We abondanded scrum. We abandoned refinements and estimation of stories and story points etc. Now we meet with a PM once a month formally and as a team perform a t-shirt size estimate on where we are. Otherwise we update her as frequently as she asks (which isn't often) or we want. This gives power to us but because of that we're conscientious and make sure to inform her timeously when things are looking sketchy or whatever. Yes, we still have to give "estimates", because ultimately, senior management want to make decisions, but it is otherwise quite lightweight.

It is so liberating.

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

#306
post #76

Earlier quoted context omitted.

Another option is to work at a consultancy where you hop aboard a new customer project every 3-6 months. Approach every customer as an opportunity to do some resume-driven development and pick a bunch of untested new technologies to experiment with. Be sure to do at least a couple of presentations to tell everyone about the hottest new things you are doing to bring value to the customers. Leave the project once it sl…

For maximum results, trade-off with a buddy: Spend Q1 each crashing your respective project; spend Q2 as a fixer undoing that damage using his knowledge of his own work. You’re both cutting edge and a proven fixer!

Reminds me of The Good, The Bad and The Ugly.

Tuco is a wanted man, Blondie brings him in and gets the reward money. Then just as Tuco is about to hang, Blondie shoots the rope and they both escape to another state ... where Tuco is also a wanted man.

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

#307
Its tricky to get credit when your skills are x10 or higher compared to your team. 2 companies ago, a team of 40 engineers took 4 years and $29M to do a generation product update. The next company I worked for took $1M 5 engineers and 2 years (product from scratch). My current company I did the whole thing myself in 14 months (@ < $0.5M), basically on autopilot. Unfortunately, the stakeholders are unaware that they got enormous value by being lucky of hiring the right person for the project. And I still fight management/budget constraits and hot headedness. Almost enough to drive me to next employer.

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

#309
This is kind of a problem with preventive ethics in general. It seems to me that given two bad choices, the best option is actually neither - that is, to prevent the choice from being necessary. To use the common example of the trolley problem, the best answer isn’t to choose one option or another, it’s to prevent the trolley from being about to run someone over in the first place.

Unfortunately the visibility of these non-events means that their heroes go unnoticed. Noticing them would require a fundamental reorganization of how we perceive time and the future.

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

#310
post #289

FTFY: nobody ever gets credit if they don't publicize their successes. By default, fixing problems before they happen doesn't make headlines, so you have to find clever ways to earn publicity. One politician classic: let it become a "problem" enough to earn publicity, THEN fix it. Two examples: Y2K and Healthcare.gov

spot on. As a general rule of thumb I keep a form of activity/issues log and send a monthly summart to the finance guys and head of dept along with "expected issues". Letting things crash and burn is a thing I learned from one of my managers a while back. It's great for raises, bouses and rep. Takes a good deal of effort not to fix things I know will break though.
Post reply on HN