# What vs. how

2018-03-12

> 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.

Between the two? JavaScript :p

Other articles in English: On caching links, Bushcraft retrospective, Into the Raft, Into the Bugs, Meritocracy crisis, 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, Distributed teams, Into the Wild, Without JavaScript, Inclusive Python, Micro-cultures and governance, Resilient Web and Tools, Bitcoin and energy, Team building, Inclusive developer, Cultural Intimacy, Tools and teams, Senior developer, Slow Data, Inclusive communities, Delivery and value(s), Collaboration debt, Communities and leadership, Specifications and APIs. Oh, and most of the 2018 thoughts.