Back
AI EngineerVideoSource LinkedagentNew
How to Get Your Org to Adopt Coding Agents (Without Shipping Garbage) — Eyal Blum, Figma
Write executable checks before implementation, then split agent plans into independently validated, reviewable phases.
AI EngineerAI EngineerAI EngineerAug 28, 20262 min
Source Summary
Figma’s cautious agent adopters expose missing safeguards, not resistance. Use their feedback to improve verification, plans, review size, and the labeling of AI-generated work.
Practical Implication
Make verification executable before implementation: use TDD, encode repeated checks deterministically, and split plans into independently validated, reviewable phases. Put the reason for the change first, and use skeptical maintainers’ feedback as the safety roadmap.
Agent-Ready Context
Figma reports uneven agent adoption and says experienced engineers may be slowest because they see codebase risks first. One detailed plan turned an estimated **six weeks of coding into about one week**, including review. Make verification executable before implementation: use TDD, encode repeated checks deterministically, and split plans into independently validated, reviewable phases. Put the reason for the change first, and use skeptical maintainers’ feedback as the safety roadmap. The workflow is still evolving and depends on planning and review effort that raw generation metrics can hide. AI also increases communication volume, so clearly separate human-written intent from generated descriptions to protect scarce reviewer attention.
Context Map
Rate This Item
Personal Note
No note yet. Notes are included in exported bundles.
Related — Every Edge Explained
No approved edges yet for this post.