Communication friction in development

Short summary

As AI agents increasingly handle code generation, communication—not coding—becomes the critical bottleneck in software teams. The post maps friction across requirements, documentation, chat systems, and code review, then proposes solutions: write architectural decisions, explain the "why", maintain status visibility, use templates, and escalate ambiguous topics to synchronous discussion.

• •AI shifts focus from coding to communication; clarity and context are now the constraint
• •Document decisions with ADRs, explain rationale, maintain visibility, use templates
• •Escalate ambiguous topics to synchronous conversation to avoid misinterpretation

Generated with AI, which can make mistakes.