MANIFESTO #funny
A quick follow up to hiring in 2026
Challenging conventional wisdom in AI and software engineering. Deep explanations, mental models, and practical heresies for building better systems with less bullshit.
A quick follow up to hiring in 2026
Eng hiring in 2026 still runs on ATS filters and trivia theater. What I'll hire for instead: philosophies that survive hard problems, proven in a
It reviews its own security, checks its own quality, and writes its own docs so I can launch a dozen of them and step away. I benchmarked it
I swapped models three times to fix one flaky test. None of it helped. Every reliability lever in AI-assisted development lives in the layers you
Since the last release I wrote up, agentic-os got about 47% smaller, grew a set of hooks that fight its own context drift, turned them on by
A government just switched off a frontier AI model overnight. Why security not velocity is now your top engineering metric.
My four LLM reviewer agents kept re-discovering the same findings, run after run. The fix: tier the checks, ledger the noise, and promote what
AI made every engineer faster and your team slower to ship. The velocity is on the dashboard. The collaboration tax that pays for it isn't, and I
You're using maybe a third of what `.claude/` can do. Here's the complete modern anatomy organized by directory and scope precedence and the
Senior engineers have been quietly building AI scaffolding that juniors never get access to. I just open-sourced mine.
Seven posts explaining the system. This one shows it a real engineering task, start to finish.
Hooks wire your AgenticOS to session events. They're the automation layer that removes the work you'd otherwise have to remember to ask for.
Parallel agents stomping files is an isolation problem, not a parallelism problem. Here's the worktree pattern that fixes it.
CLAUDE.md is where your AgenticOS rules live. It governs every session, every agent, every project.
The layer that makes your AgenticOS learn, one non-obvious fact at a time.
The constraint is the feature. One agent definition file is more reliable than any prompt you've ever written.
Intake quality is the ceiling on execution quality. Here's how to build a shaper that scopes briefs before any agent touches a file.
Skill files are the atomic unit of a Claude Code AgenticOS. Get this layer right and every agent you build downstream becomes composable.
An AgenticOS is a composable, version-controlled layer that makes AI behaviour consistent, reviewable, and delegatable and you can build it in a
CAP says pick two, but partitions aren't optional. So you're really choosing Consistency or Availability *during* a partition. And PACELC is the