@PawelHuryn: 7 truths about working with coding agents, learned the hard way: 1. /goal is not enough. Explain the why + strategic co…
Summary
An experienced developer shares 7 key insights on effectively working with AI coding agents, emphasizing the need for strategic context, documentation, and human oversight for better outcomes.
View Cached Full Text
Cached at: 09/16/26, 04:09 PM
7 truths about working with coding agents, learned the hard way:
-
/goal is not enough. Explain the why + strategic context (market segments, value proposition, how you make money, etc.). Progressive disclosure. That’s what enables agents to make better, more autonomous decisions.
-
To review code, agents need something to review it against. In particular, it’s critical that agents document the intent, for example, roles and permissions. Without it, they may not be able to distinguish a bug from a feature.
-
Documenting the intent is also a prerequisite for reliable tests.
-
Even with browser automation, agents still can’t review UX effectively, especially dynamic elements, micro-interactions, window resizing, and so on. Asking the agent to take screenshots and inspect them (exploratory testing) helps a lot, but in 2026, you still need a human eye.
-
Human code review is necessary only in the absence of strategic context and documentation.
-
If you must review something technical, review the architecture and procedures - not the syntax. How can you make your procedures, e.g., release, more deterministic?
-
You will get way better results by letting Astra and Opus/Fable work together. Neither OpenAI nor Anthropic would tell you so.
Similar Articles
Building agents taught me the model is rarely the problem. What's your hard-won lesson?
A developer shares hard-won lessons from building AI agents: focusing on tool design over model choice, using small loops instead of giant prompts, logging agent context, adding guardrails early, and creating small evals to catch bugs.
A developer shares insights on how to maximize AI agent capabilities, arguing that simpler setups and understanding core principles are more effective than complex harnesses and libraries.
A developer shares insights on how to maximize AI agent capabilities, arguing that simpler setups and understanding core principles are more effective than complex harnesses and libraries.
The Real Truth About AI Agents
An experienced practitioner shares hard-won lessons from deploying 25+ AI agents to production, arguing that memory, orchestration, and auditability matter far more than model choice. The article details common failure modes like context loss and silent cost loops, and recommends a stack including Claude Sonnet 4, Pydantic AI, and dedicated memory layers like Octopodas.
@bibryam: Using Agents, Keeping Agency. https://devindickerson.dev/posts/using-agents-keeping-agency/…
A blog post warns that AI coding agents often default to popular but unsuitable technologies, incurring technical debt, and urges developers to retain agency in architectural decisions.
@TheAhmadOsman: For agents like Codex Cli, OMP, Pi Claude Code, Droid, OpenCode, etc There’s a crucial recipe: 1. Modularity 2. Domain-…
A developer shares a recipe for building effective AI coding agents: modularity, domain-driven design, explicit specs, and thorough documentation, arguing that discipline matters more than model capabilities.