@RuthMalan oof, I need to finish my templating on the blog — the underlying data it’s using has all kinds of atuff about where the talk was given, etc. it’s from Confab, in early 2023!
@jmeowmeow@RuthMalan yup. That quest to find and articulate the useful stuff beyond “works on my machine/for my project/in my org” feels like it can be a lifetime’s work, lol
@RuthMalan man, your stuff is always such a treasure trove.
And I hear you about evolving — one of the reasons I’ve been building more of an archive of older writing and talks is how easy it is to lose the layers of change, and just remmeber the “conclusion” of 10y of iterating on a subject…
@dachary Qwen 2.5 is the best of the local models in my testing for the same purpose — and the same gap w/gtp4o mini. The biggest thing that jumped out for me was to stay alert for taxonomy decisions that rely on intentions outside of the documents themselves (ie this is for beginners). Nice to see you’re seeing similar results!
That is, conversations include accidental and intentional informal conversations, as well as intentional (deliberate) deliberations that really work on an issue — over time (as we understand more, as things change, etc.) too.
The architect role, by whatever name, gives some organizational commitment to sustaining that system expertise, attention and relationship space — in part to provide anticipatory awareness and continuity of attention to system capabilities, properties, and challenges.
@SwiftOnSecurity it’s an absolutely insufferably “podcast guy” kind of narrative but Zen and the Art of Motorcycle Maintenance is so closely related to these themes for me; curious if you’ve read it.
It touches on both the pursuit of “quality” as an inherent elegant match between the tool and the task, and the poisonous “freshman’s disease” of learning enough to be frustrated and stalking off to change the world without studying the insights of those who’ve gone before.