Not All Laziness Is Created Equal

How to tell the difference between productive laziness and plain indifference in software development There is a famous idea in management circles, traced back to the Prussian military, that the best leaders are the smart-lazy ones. Not the diligent ones who never stop working. Not the dull ones who coast. The ones who are intelligent enough to see what needs doing, and lazy enough to want to do it in the fewest possible steps. It sounds like a paradox. But anyone who has worked in a software team long enough has likely met two very different people who would both describe themselves the same way: lazy. One of them builds composables, abstractions, and reusable systems. They hate solving the same problem twice. Their code is a gift to the next developer. The other can't be bothered to make anything reusable. Their codebase is a maze of tightly coupled components, copy-pasted logic, and patterns that were never meant to scale. They just needed it to work today. Both call themselves lazy