Yesterday I was ready to get some changes into master, so I merged in the latest and opened a PR. But NO, the build on my pull request broke.The error was: ERROR: (jsdoc-format) /long/path/to/file.ts[52, 1]: asterisks in jsdoc must be alignedERROR: (jsdoc-format) /long/path/to/file.ts[53, 1]: asterisks in jsdoc must be alignedERROR: (jsdoc-format) /long/path/to/file.ts[54, 1]: asterisks in …
The inaugural REdeployConf wrapped up yesterday (as I write this). I’m already feeling withdrawal from intense learning and conversations. I’ll attempt to summarize them in this post. The RE in REdeploy doesn’t mean “again” (lo, it is the first of its kind). RE stands for Resilience Engineering. It is a newish field, focused on sociotechnical …
In Why Information Grows (my review), physicist César Hidalgo explains that the difference between the ability to produce tee shirts vs rockets is a matter of accumulating knowledge and know-how inside people, and weaving those people into networks. Because no one person can know how to build a rocket from rocks. No one person understands …
The other day in Iceland, a tiny conference on the Future of Software Development opened with Michael Feathers addressing a recurring theme: complexity. Software development is drowning in accidental complexity. How do we fight it? he asks. Can we embrace it? I ask. Complexity: Fight it, or fight through it, or embrace it? Yes. Here, …
Or: the Origins of Opera and the Future of Programming. (video, or TL;DR, or abstract) At the end of this post is an audacious idea about the present and future of software development. In the middle are points about mental models: how important and how difficult they are. But first, a story of the origins …
Read moreCollective problem solving in music, art, science, and software
Does caring scale? We can’t all care about everything. We have cities without clean water, a criminal justice system full of injustice, and oceans clogged with paper bags. There are too many important causes to catalogue, much less champion. We can only contribute to a few. We can’t all care about everything. At my house, …
Understanding code under change Why is it so hard to jump into a team and start contributing to code? Why is someone else’s code so darn incomprehensible? One reason is that the code is a snapshot of a system in process. If you know where it was and where it’s aiming, the middle makes more …
When you learn to code, you acquire a superpower: automation. We turn the computer into a machine to do our (very specific) bidding. We get paid to automate what other people want. We can and should use this superpower for ourselves too! Levels of automation Are we programmers or software developers? Probably both. I think …
(This post continues from the Royal Yak, and concludes the series A Taxonomy of Yaks.) When we improve how we work, we make tasks faster. We make progress smoother. This is magnified when we improve how all our team members work, or our whole community. Now and then, though, an improvement turns into something more: …
(continued from Trim Yaks; part of the Taxonomy of Yak Shaving series) Royal Yak, aka Yakkity Yak (quote from yakbreeder.com) Talking to people is yak shaving; it is an intermediate task that helps you get your official tasks done. It’s usually seen as a separate way to “waste” time. I’m here to call relationship-building out …