The review burden problem mirrors what happens with internal tools generally. Teams use AI to spin up an internal system in a weekend, everyone's impressed, then six months later someone's spending half their time maintaining it. The build was never the expensive part. The review, the edge cases, the ongoing maintenance - that's where the real cost lives, whether it's OSS contributions or internal tooling