An old-school blog where I write with uneven frequency on whatever seems interesting or important to me at any given time. Typically these subjects tend to center around:
But anything is really fair game here. If you wish to subscribe to updates, I publish an atom feed for use in your favourite reader app or you can follow me on mastodon. I speak at a number of conferences, my speaking schedule is maintained over here. I also host live Software Architecture Workshops and do occassional private training, speaking, and consulting gigs.
Thanks for stopping by my little corner of the web.
Metaphysics and Software Architecture? Hear me out…
Suppose I roll a red ball across the floor.
Where did the redness come from?
Plato might say it comes from the abstract “Form of Redness.” Aristotle might argue it’s a property the ball possesses. Hume? He’d ask you to stop being weird and go touch some grass.
Now… where do architecture illities come from?
Yesterday marked the conclusion of a whirlwind week in Bengaluru at the Great International Developer Summit. As I embark on my long journey home (30+ hours of travel) I am left both energized and humbled by all I have experienced.
Why does it feel like so much of tech is just reinventing the same ideas every few years?
I have a theory…
Software architecture was never easy, but today it feels more challenging than ever. Why? Because the role of the architect has evolved far beyond selecting patterns and designing systems—today, an architect must navigate complexity on multiple fronts simultaneously.
My friend, mentor, and former boss, Robert Harris, recently posted about a novel approach he takes to making tech debt more tangible; he makes people fill out a credit slip whenever they take on tech debt. It’s worth reading his post (and giving him a follow).
As always, I have some thoughts on this topic…
In Part I we explored the idea of AI agentic systems, current paths being explored, and the roadblocks present in those paths. If the API-driven approach is “too hard” and the browser-driven approach is “too soft” does there exist an approach that is “just right?”
I’ve been designing and building data-driven & machine learning-enabled applications, on and off, for roughly 15 years. Although I was fortunate to have access to GPT3 about a year ahead of the mainstream, I was wholly unprepared for the wide-reaching impact of this technology. The introduction of ChatGPT in late 2022 brought into sharp focus just how impressive the current generation of large language models have become. The sheer breadth of zero-shot capabilities demonstrated by a single model has everyone’s minds racing. There is obviously immense power here, but how do we harness it to realize its true value and potential? That is the trillion-dollar question.
One of the most compelling visions for humanity’s next steps with AI is creating autonomous agents; AI systems that can do more than summarize text and provide plausible, information-shaped responses to our prompts. These are AI systems that can interact with other systems or the physical world. Although a great deal of R&D is underway as I write this, I’m shocked that one of the most promising solutions to the conundrum of how to achieve such agentic systems continues to fly under the radar…
Welp, the final draft of my book, Mastering Software Architecture has been turned into the publisher. It is the culmination of nearly two years of active writing (~800 hours), countless hours of research, 156 citations, and 25+ years in industry.
Rather than write yet-another distillation of the current state of practice, I have tried to dramatically improve it. The model introduced in this work unifies our fragmented models in a way that solves real problems once thought by many to be intractable.
I’m proud of the result.
You can be more than a label, or category. In fact, the breadth of your knowledge and experience is your superpower in whatever field you work.
Being a magician made me a better technologist, and my experience in the tech world made me a better magician.
Microservices architecture has become a buzzword in the tech industry, promising unparalleled agility, scalability, and resilience. Yet, according to Gartner, more than 90% of organizations attempting to adopt microservices will fail. How can you ensure you’re part of the successful 10%?