Never attribute to stupidity what is adequately explained by opportunity cost
1–10 of 94 posts
Re: Never attribute to stupidity what is adequately explained by opportunity cost
#2Re: Never attribute to stupidity what is adequately explained by opportunity cost
#3I've definitely fallen into the "attribute to malice/stupidity" trap as well, even when I know that the people responsible are working flat out, if you're not in the trenches it's so easy to say "but it's so simple! I could do it in an hour". It's something you have to constantly keep in check.
Honestly, I think the prioritisation thing is absolutely the most important thing any team or company can do. The person working on a feature almost never has the overall context to accurately prioritise. The next feature or bug on whatever they're working on will always feel more important than someone else's problem. Building a working environment which empowers people to work towards a common goal - and not just whatever feels important to them in the moment - is really hard.
Re: Never attribute to stupidity what is adequately explained by opportunity cost
#4Re: Never attribute to stupidity what is adequately explained by opportunity cost
#5Re: Never attribute to stupidity what is adequately explained by opportunity cost
#6"It's not a matter of convincing me we should do this. Obviously, we should. But we also have a hundred other things that we should do, and a few dozen things that we need to do. So it's not a discussion of 'should we'; it's a discussion of understanding how important this thing is in relation to all of the other things."
Triage and prioritization is hard.
Re: Never attribute to stupidity what is adequately explained by opportunity cost
#7Ok, let's leave security for later!
Re: Never attribute to stupidity what is adequately explained by opportunity cost
#8I also wrote about this recently: https://timwhite.digital/building-software-sharing-knowledge
Re: Never attribute to stupidity what is adequately explained by opportunity cost
#9You just have to look at the k8s hype to see that it's not.
In this industry, I often have the feeling that people are fetishizing complex solutions even if the problem at hand doesn't require them.
But I have to admit, it's not easy to focus on the problem space and really work out what is needed. Most people do too much or not enough.