Exploring the echoes reverberating through time left by the technology of yesterday as we embrace the technology of tomorrow.
Christmas week, so most of the news is the year itself sitting up and asking to be summarized. Nvidia buys Groq for $20B in the largest deal in company history, Z.ai ships GLM-4.7 as the new top open coding model, and the Challenger AI-layoffs number lands at 54,836. A partial year-end take.
Decisions as Code specifies the standard. OPA Gatekeeper enforces it. Constraint templates as the policy definition layer. Required tags, model version pinning, namespace quotas, network policies for AI workloads. The 'specify, then verify' loop, finally complete.
The category I've been writing about for two years arrived faster than the broader industry conversation acknowledges and slower than the early enthusiasts expected. The shape of what's actually here is more nuanced than either timing claim alone suggests.
The atomic-unit metaphor in software isn't decoration. It's a working design pattern: small immutable typed primitives (atoms) compose into larger functional units (molecules). What makes the metaphor useful, versioning, lineage, composition rules, and what makes it a marketing trap.
A nine-month checkpoint on the takes I had in March 2025 about how the year would shape up. Some held; some bent; some were plain wrong. Worth being explicit about which is which.
The week the model arms race went thermonuclear: GPT-5.2 lands as the answer to a 'code red' memo, Google ships Gemini 3 Flash three days later, NVIDIA drops Nemotron 3 as open weights. Meanwhile Trump signs an EO to preempt state AI laws and Accenture's AI-driven RIF crosses 11,000.
The Copilot+ PC marketing pushed NPU silicon into mainstream Windows hardware in 2024-2025. The hardware shipped; the software story hasn't caught up to Apple's. Worth being honest about where each platform actually stands at the end of 2025.
Every platform starts with traceability as a goal. Most lose it by month six. The predictable failure modes, log-format drift, ID-namespace collisions, the 'we'll add structured logging later' debt, the asymmetric incentive to write logs but never read them. What survives, and why.
What integrating an open-weights model into a small SaaS product actually looks like end to end, the architectural decisions, the operational reality, the cost economics. Less hand-wavy than the typical write-up.
Trump signs an executive order to preempt state AI laws. OpenAI rushes GPT-5.2 out under a self-declared code red. Disney puts a billion into OpenAI and licenses 200 characters into Sora. Accenture pledges 30,000 Claude practitioners. The week the AI story stopped being about models.
Argo Workflows for the long-running, branching, fan-out AI ops pipelines that don't fit a CI runner. RAG indexing jobs, fine-tuning runs, eval suite execution. WorkflowTemplates as the Decisions as Code surface, same pipeline shape, different inputs per project.
DSPy is the framework that's most-likely to look obvious in retrospect. The practitioners running it in production have learned things the documentation doesn't cover. Worth the field report.
