Exploring the echoes reverberating through time left by the technology of yesterday as we embrace the technology of tomorrow.
The right unit for AI cost tracking isn't tokens, isn't requests, isn't users. It's conversations. The cost story makes sense when you measure it that way and gets impossible when you don't.
The IDE-agent products that have stuck for me through a year of daily use share one thing: a strong plan-then-execute workflow. The tools without it produce flashier demos and worse outcomes. Worth being explicit about why this is the actual product.
The personal AI assistant pattern wants to read everything you have. The honest engineering pattern is the opposite, design the assistant to be useful while structurally unable to see the data that shouldn't go to it. Worth being concrete about how.
What to actually buy if you're starting a home AI setup in mid-2025. Not the maximalist build; the right-size build for the workloads that justify owning the hardware.
Six months in on Operator, plus Mariner, plus Computer Use. The browser-agent category is real and the durable use cases are smaller than the demos suggested. Worth being concrete about what the category does and doesn't do well.
Tekton, Argo CD, GitHub Actions, Jenkins X, four answers to model deploys. You can't unit-test a model, so eval suites become the test substitute. Versioning, rollback, blue-green serving. Pipeline config as the Decisions as Code surface, projected per environment.
The conversation history with your AI tools is a piece of infrastructure now. Treating it like ephemeral chat is fine for the casual case; treating it that way for daily work means you lose context, repeat yourself, and slowly poison your own retrieval.
Halfway through the year. The frontier moved, the workhorse tier got crowded, the price floor dropped. The honest leaderboard isn't a single ranking, it's a routing decision per workload, and the menu in July looks meaningfully different from the menu in May.
Two years ago, every other LinkedIn post promised six-figure salaries for prompt engineers. Today the title's mostly gone from job boards. The work didn't go away. The framing did, and it's worth being clear about why.
Twelve months in, the home setup has changed shape: a Mac mini for the always-on lighter services, a Synology underneath for storage and platform services, fast portable SSDs at the working ends, and since March a Mac Studio for inference.
An M4 Max with 64 GB of unified memory comfortably runs open-weights models that needed a serious GPU rig a year ago. The price-per-capability curve crossed something quietly, and the consequence for who can run frontier-adjacent inference at home is bigger than it looks.
The infrastructure-as-code review pipeline is one of the highest-leverage places to deploy AI in an engineering org, and almost nobody is doing it well. The reasons it's underused are mostly accidental rather than principled.
