I've spent most of my career building digital commerce systems using Ruby on Rails. I've built high-volume payment gateways, the software to power fulfilment chains, rich eCommerce storefronts, and everything in between. Along the way, I've helped software organizations scale, deliver faster and work more autonomously.
In my 12 years of building software professionally, I've watched this industry's short memory distort and obfuscate great ideas until they're no longer recognizable. From Agile to TDD to object-oriented design, the core ideas are lost, but the rituals remain. I aim to elevate the valuable ideas and techniques we've lost along the way.
This website chronicles what I've learned in building large applications, running software teams, managing and consulting on products, and helping the people around me make software gooder.
Service objects, a popular design pattern in the Ruby on Rails community, are analogous to higher-order functions, and we can demonstrate that more clearly by refactoring one into a Proc without changing its API.
I recently simplified the workflow where I'm using git as my test-runner, essentially doing TCR without the R.
Should we be worried about the impact of Threads.net on the Fediverse? I summarize my thoughts on the possible outcomes and why I think we should be cautiously hopeful.
Out of the box, phlex-rails currently doesn't support parameterized layouts. I found a quick way to hack support in.
This year was a strange year, so I've been thinking about where to put my energy to distract from the ongoing collapse of civilization as we know it (or whatever.)