# Why infrastructure changes still take a week

DevFeed: [Why infrastructure changes still take a week](<https://devfeed.tech/articles/why-infrastructure-changes-still-take-a-week-17814.md>)

Original publisher: [Read original article](<https://encore.dev/blog/infra-review-bottleneck>)

Author: Ivan Cernja

Published: 2026-06-10T00:00:00Z

Content type: opinion

Language: en

Sources: [Encore Updates](<https://devfeed.tech/sources/encore-updates.md>)

Topics: [Terraform](<https://devfeed.tech/topics/terraform.md>), [Security](<https://devfeed.tech/topics/security.md>), [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>)

Tags: [iam](<https://devfeed.tech/tags/iam.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [security](<https://devfeed.tech/tags/security.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

## AI overview

The article examines why infrastructure changes often wait days or weeks for review while application code ships faster. It attributes the queue to a small reviewer pool, the high blast radius of infrastructure mistakes, and limited verification before Terraform changes are merged. It also discusses how AI coding tools have affected the queue and how teams can remove the bottleneck.

## Source excerpt

Application code ships in hours and the infrastructure it needs waits days for review. Where the queue comes from, what AI coding tools did to it, and how teams remove it.