AI-assisted development
21 articles
“Not found” is not “does not exist”
Check “not found” with bounded search, positive controls and complete output. A withdrawn-draft case separates editorial status from deployment history.
Prompt discipline is engineering infrastructure
Prompt discipline is engineering infrastructure: a forbidden-phrase catalog, hooks, and enforcement that catch AI coding agents dressing shortcuts as judgment.
One context file carried a redesign across eight AI sessions
A single CONTEXT.md carried an editor redesign across eight AI coding sessions. The ownership split that made it work: humans direct, the AI keeps the record.
Every bug report is now a patch-or-redesign decision
The minimal patch is a habit from when understanding was expensive. AI coding agents ended that economy, and most of us never consciously make the choice.
Transferable Knowledge: The Fifth Pillar of Synthesis Coding
Transferable Knowledge makes AI-assisted work useful across people, tools, crafts, time and organizations through shared decisions and maintainable code.
When All Tests Pass, Check the Whole Change
A missing field survived 1,297 passing tests. Trace it from request to database, check each service and use seven review passes to find incomplete changes.
Stop asking me: Claude Code permissions for authorized work
Reduce repeated prompts with a scoped Claude Code permission policy, distinguishing allowed commands, sandbox limits and actions that still need authorization.
The blast radius principle: checking targets before destructive commands
Use path checks, previews and a tested recovery plan to limit AI-generated cleanup commands, with a complete exercise that removes no files.
Managing AI agent skills at scale: a three-repo architecture
A three-repository architecture for public, private and team AI skills, with provenance, dependency boundaries and a method for merging local improvements.
Synthesis Skills: install methodology directly into your AI workflow
Install reusable Synthesis Skills for code review, writing, and project continuity, with current setup guidance and the lessons behind the original release.
Synthesis merging: what happens after the first PR
Integrate overlapping pull requests in dependency order, check the combined result, credit contributors and help the team take ownership of integration.
Turning code review findings into a tested upgrade plan
Turn code review findings into an upgrade plan that preserves domain behavior, addresses urgent risks and defines evidence for each change before work begins.
What reviewing real codebases taught me about code review
Reviewing the wrong branch led to better baselines, closer test inspection and clearer reports. See what comparisons prove, and what they leave unknown.
Recommend A, implement A: checking an AI agent’s work against the plan
Check whether AI-generated code follows the agreed plan and whether that plan meets the requirements, using filename collisions to test both independently.
When Someone Else Contributes to Your Synthesis-Coded Project
Review contributions against your current architecture, adapt what needs changing, and build the shared standards that let good work merge with less rework.
Code Review That Scales: Choosing Review Depth by Risk
Use a tiered code-review runbook to choose review depth, override the tier for consequential risks, and record what was checked, excluded or left unverified.
Why Engineering Judgment Matters More With AI
AI makes engineering judgment more valuable. Four experiences show how faster implementation changes refactoring, verification and what we choose to build.
Build a self-improving AI coding practice
Improve AI coding through project context, skills, instructions, and practice. A team account and CSV exercise show how to carry useful lessons into later work.
Understanding the AI-generated code you ship
Understand AI-generated code well enough to debug and change it. A cache example connects comprehension, review, and tests to sustained development speed.
Quality standards for AI-generated code
Design a testing strategy, review generated code, and connect passing checks to real requirements. An empty-response example shows how a green suite can fail.
Human architectural authority in AI-assisted development
How engineers keep AI-assisted development coherent: own architectural decisions, record their rationale, and use shared constraints to reduce costly rework.