Infrastructure changes consistently lag behind application code in review time, often taking days or weeks while code ships in hours. Three root causes drive this: a tiny reviewer pool, high blast radius of infra mistakes, and lack of automated verification before merge. AI coding tools have made this worse by accelerating code output without speeding up infra review. Teams address this by hiring more platform engineers, loosening review (rarely), building internal developer platforms with policy checks, or eliminating the separate infra change entirely by declaring infrastructure in application code. The post advocates for the last approach, using Encore to co-locate infra declarations with application code so features ship as a single PR.

6m read timeFrom encore.dev
Post cover image
Table of contents
Why the review is slowWhat AI tools changedThe ways outWhat skipping the queue looks like
492 Impressions