Developers are attached to tools because tools encode trust

gist

Ryan Donovan argues that developer trust comes from predictable tools embedded in familiar social and technical processes, which agentic coding disrupts through speed, opacity, and probabilistic output. As code generation becomes cheap, requirements, review, operational cost, and accountability become the hard parts. Teams rebuild trust by making expectations explicit, preserving human ownership, supplying verified context, reusing proven components, and keeping deterministic code where uncertainty adds no value.

ideas

• Trust is practiced predictability. Developers trust tools whose boundaries, behavior, and place in the surrounding workflow remain understandable through repeated use.
• Cheap code moves the bottleneck. Agentic generation increases the importance and cost of precise requirements, code review, production validation, and operating discipline.
• Tooling cannot repair culture by itself. New controls help only when teams also change shared processes, collaboration, and responsibility for outcomes.
• Human ownership stays explicit. The people who submit and approve agent-produced changes remain accountable for the code and its consequences.
• Context and determinism are controls. Teams should capture tacit knowledge, reuse proven components, and keep stable scripts where probabilistic generation adds risk without value.

quotes