Individual Engineer Agency

How much control does a single engineer have over the product they work on? Less than most engineers assume.

In team-based software development, individual contributions get absorbed into a larger system. You can write excellent code in your area, but the user experience is shaped by organizational incentives, product strategy, technical debt accumulated over years, and the work of every other engineer on the team. Sean Goedecke argues in working-on-products-people-hate that this limited agency is one of the hardest things for engineers to accept, and that working on unpopular products is what forces the realization.

This doesn't mean individual work is pointless. It means the relationship between "I did good work" and "users like the product" is weaker than it feels from the inside. Engineers who only ship beloved products can mistake favorable conditions for personal skill. Engineers who ship hated products and assume it reflects their ability make the opposite error.

The practical takeaway: focus on the quality of your local contributions and the incremental improvements you can make. Accept that product perception is mostly outside your control. This is less satisfying than believing you can hero your way to a great product, but it's closer to how software actually gets built at scale.