Essays by Ry Walker

Enterprise agents need layered interfaces, real software skills, and flexible platforms. The harness around the model matters more than the model.

Enterprise AI will not be one mega-agent. It will be a mesh of atomic, auditable units, and the companies that nail review and context will own the next infrastructure layer.

Models keep getting better, but agents without deep codebase and organizational context are just expensive autocomplete. Context engineering is the bottleneck nobody has productized.

Every quarter a new model writes marginally better benchmark code. And every quarter enterprise teams stall on the same context problems. The hard part is the engineering around the AI.

The gap between an AI demo and an AI deployment is called software engineering. Most organizations are not equipped to close it, and that is where all the value lives.

Trust is the bottleneck for agent adoption, not capability. Hide the logic in a prompt and people stop using it. Make it inspectable code and they iterate with you.

When the same object has three names, your architecture is drifting. Tasks, runs, threads, chats — all of it is just a session. One container, many shapes of work.

Automations bundle trigger, prompt, tools, and model into one flat object. That works at five. It falls apart at fifty. The agent has to become its own primitive.

When an agent ships a working PR every six minutes, you accumulate reviewable code faster than humans can process. The next wall is review, not generation.

Automating your GTM motion, vendor onboarding, or SKU rationalization is software engineering. The end user being internal does not change the discipline required.

Role-based agents start with the hardest version of the problem. Workflow-first agents start small, ship in a week, and compound into something larger.

The industry treats agents as a new category. They are not. Agents are software, and the same engineering principles that have always mattered still apply.

A visual guide to the emerging AI agent ecosystem — from foundation lab tools to enterprise in-house agents, and everything in between.

A first-hand take on Claude Code 4.6: better context retention, smarter questions, and a workflow that finally feels like real pair programming.

Developer performance is hard to measure; AI adds noisy signals. A case for outcome-focused frameworks over vanity metrics.

Most developers use AI only to write code. The real opportunity is using AI to secure, debug, and test—deploying equal firepower on defense.

AI-assisted development has changed the economics of code quality. Teams shipping "good enough" code are moving faster than craftperfectionists.

Humans over-engineer. Humans pick wrong abstractions. We normalized human imperfection and treat AI imperfection as disqualifying. The bar is not as high as we pretend.

Most developers deploy AI almost exclusively to ship features faster. The asymmetry is the problem — not the AI itself.

Survey results from 399 developers reveal what's broken in modern software development: focus time, AI tools, and distribution top the list.

The three tiers of AI coding adoption: from assisted tools to autonomous background agents. Why 80% of code will be AI-written within a decade.

AI coding is not about replacing developers. It is about expanding who can request software work in the first place — and 10x-ing total demand.

AI coding adoption is happening in three distinct tiers — assisted, guided, and fully autonomous. Most teams are stuck in tier one and do not realize the gap.

The AI-First Software Development Manifesto: 11 principles for treating AI as a true development partner, not a fancy autocomplete.