Interesting observation.

One thing I’ve noticed while building internal tooling is that LLM coding assistants are very good at generating infrastructure/config code, but they don’t really help much with operational drift after deployment.

For example, someone changes a config in prod, a later deployment assumes something else, and the difference goes unnoticed until something breaks.

That gap between "generated code" and "actual running environment" is surprisingly large.

I’ve been experimenting with a small tool that treats configuration drift as an operational signal rather than just a diff. Curious if others here have run into similar issues in multi-environment setups.