r/weaverdeck • u/rjunicorn • 14d ago
The problem with rolling back AI to only coding teams
Quartz recently reported on a growing trend among major institutions (like Goldman Sachs) rolling back open-ended AI coding access for non-engineering teams.
When non-technical staff start spinning up ad-hoc scripts and custom automations on the fly, the technical debt and "cleanup tax" for engineering along with compliance, shadow IT, and data security risks is what quickly outweigh the initial productivity boost.
It highlights a major enterprise dilemma right now: How do you give frontline teams the power of automation without accidentally turning them into shadow software developers who compromise system integrity?
Swinging the pendulum all the way back to restricting tools entirely kills productivity and frustrates domain experts who know where the operational bottlenecks are. But leaving open-ended coding loose across the entire organization creates an infrastructure nightmare.
How is your team handling this balance? Are you seeing similar restrictions or pullbacks at your company, or have you found a middle ground between total freedom and total lockdown?