Comment by darkwater
21 hours ago
Just...wow. That sounds awful, and I'm sorry for you, but I believe many other companies will or are already following that same path.
And myself being an infrastructure guy that needs to maintain all these PoCs that are now suddenly critical for production, it's the perfect nightmare.
And mind you, that dynamic always existed to a certain degree (laptop on a desk that runs some ugly Python script that does half the work of the BizOps team? Check. GCP account attached to the GSuite running a random instance for finance when the company is 101% on AWS? Check. Spreadsheet with macros that sends emails via Outlook as a mailing list manager? Check.) but at least when you discovered that you could scold them and tell them that we need to migrate this to a proper system because security. But nowadays with vibe-coded internal apps...it's a challenge.
It would be fine if my boss actually followed the docs, or just pointed his agent at the docs.
Whats more annoying is that he changes AI provider lots, so we can never inject rules/skills to make sure he uses the right pathway from the start.
There is probably some opportunity here for a centralized, internal only LLM proxy which injects AGENT.md and skills and permits switching backend providers.