Operations | Monitoring | ITSM | DevOps | Cloud

Last month I was making a change to sx, our CLI. I updated a core flow, adding external catalogs as a source for sx add. Small change. Then came the testing. I knew I was messing with a core flow and wanted to be sure I hadn't broken anything. I spent about forty-five minutes setting up an isolated environment. Spinning up Docker. Fighting with tmux. Getting a clean install state I could run through the TUI a few times. Forty-five minutes of my afternoon that produced zero code. I complained in Slack.

Let me paint a picture. Your company has rolled out Claude or ChatGPT as the standard AI tool. You've connected MCPs to Stripe, your HRIS, Datadog, your CRM, and Slack. A senior engineer set this up because they needed to answer hard cross-system questions and it works beautifully. Now a marketing intern sits down, opens the same LLM harness with the same MCP config, and types "show me revenue by customer for the last 12 months." They get it.

Here's something nobody talks about at the AI strategy meetings. Your organization just spent six figures on Cursor licenses, Claude seats, and Copilot subscriptions. Ninety percent of your engineers have access. By most internal measures, the rollout was a success. But somewhere on your team, one developer is running circles around everyone else.