Critical developer skills in 5 minutes or less.
Half my own learning journey, half experiment to improve software education. These posts attempt to extract best practices from, and connect readers to, leading software literature.
The Resemblance and Likeness patterns improve the readability and diagnosability of developer tests.
This is my first time event storming a different system in an industry I’ve worked with previously. I’m surprised how effective the second layer modeling has been for differentiating businesses within the same industry.
A former FBI hostage negotiator discusses how to apply FBI negotiation techniques to business and everyday life. I was surprised that the approach is mostly about listening really well and helping the other side feel heard.
What could Net Promoter Score tell us if we apply it differently?
I’ve thought a lot about how to measure development outcomes, but never been satisfied with my answers. I think I may have a bit more clarity thanks to a new perspective.
Notedown is my convention for note taking in Markdown. Now it’s also a library that reads the convention as semi-structured data.
AI has made a big splash in the media, and for good reason. But I don’t think AI is likely to eliminate programmers any time soon.
Architecture Without Architects introduced me to urban planning as a metaphor for software architecture, and I love it.
Star Trek holds some surprising insights into leadership.
I’ve been refining my knowledge of Event Storming and I found the contrast between commands and events an effective tool for explaining the process.