I’ve been thinking a lot about the difference between expertise and value. I'm someone who just wants to build products. I learn things like TypeScript or React only to the extent that I need to get something working. I don’t dive deep unless my product demands it.
But most of the industry seems to reward broad or deep expertise, knowledge of systems, protocols, or architectures, even when it’s not directly tied to delivering user value. This makes me wonder: am I doing it wrong?
It feels like we often judge engineers by how much they know, not by what they’ve shipped or how much impact they’ve had. It creates this pressure to keep learning things that might not ever help with what I’m actually trying to build. Has anyone else struggled with this? Is optimizing exclusively for value a valid path long term?
Would love to hear how others think about this.
That is, the bosses son isn’t going to feel there is a contradiction here but you’re going to feel it when they try to explain to you why he got a promotion and he didn’t.
Now some places are healthier than others and some are more fair than others.
I think to get the whole picture you have to be able to hold a few different viewpoints about a situation. In the end you deliver value as part of a team and that can have many corollaries such as: prioritizing what works for the team as opposed to myself (so far as I get what I need and feel OK about it), getting some of my personal development through side projects, recognizing that my team puts limitations on how much value I can make and deciding how much I want to live with it, press for change in the organization or move on.