What vs. how
His enthusiasm for changing the world is replaced with nit-picking the development process.
Worse of all, though, his concern that “We aren’t building the right thing” will be replaced with “We aren’t building the thing right.”
He’s learned to not give input on
what is built, so he becomes obsessed with how it’s built.
Your culture, for him, has become survival of the fittest.
( Why your programmers just want to code cache)
Related to yesterday’s note on
complex vs. complicated, focusing on the how might be an auto-defensive attitude toward an uncontrollable environment. Complicated code as a fallback to complex relations, something you can build upon without the versatility of humanities.
← Complexité ou complication ? | ↑ | Corporate responsibility →
Other articles in English:
The Seller, the Teacher and the Wise,
Into the Good,
Into the Mice,
Into the Camp,
Into the Wind,
Into the Snow,
Into the Cold,
Async Python Frameworks,
Into the Wild,
Micro-cultures and governance,
Resilient Web and Tools,
Bitcoin and energy,
Tools and teams,
Delivery and value(s),
Communities and leadership,
Specifications and APIs.
Oh, and most of the current thoughts.
[Travailler ensemble ?] ·