Operations | Monitoring | ITSM | DevOps | Cloud

On June 24, 2026, Shopify experienced a widespread service disruption that affected storefronts, admin dashboards, and merchant access across multiple regions. While the outage did not impact every user, reports quickly surfaced from merchants around the world who were unable to access stores, log in to administrative tools, or complete routine operations.

Enterprise IT networks power business operations across the world. As businesses scale to catch up with an increasingly-demanding user base, networks also grow more complex. IT teams managing these networks have to monitor more data than before, under more stringent SLA terms, with little room for failure. Trying to do this manually across thousands of devices can take a lot of time and effort, and are prone to errors.

Agentic coding tools like Claude Code can write, refactor, and debug across an entire codebase, but by default they read code as plain text, the way grep does. The Language Server Protocol (LSP) changes that: it’s the same code-intelligence layer an IDE uses, and wiring it into an agent lets it read code by meaning instead of by string match. The bigger the codebase, the more a wrong guess about a symbol costs, and the more that structural view pays off.

Interface counters tell you a port is busy. Bytes in, bytes out, errors, drops. That’s enough to know a link is saturated, but not enough to know which conversations are saturating it, which devices are involved, or how a problem propagates across your network. For that you’ve traditionally needed dedicated network performance monitoring tools, usually expensive, usually a separate console from the rest of your monitoring.

Since I started using Claude Code more frequently, I kept noticing a “worktree” checkbox popping up whenever I started a session in a Git repository. I had no idea what it meant, so I did what any curious developer would do and started digging. What I found was a Git feature I somehow never came across before: git worktrees.