JUST IN: Starbucks retires AI inventory tool across North America after it reportedly miscounted & mislabeled store items.

Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10 years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored). If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update! I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it. Feeling pretty swell about this mentality with all the supply chain attacks happening.

Anthropic acquired and is shutting down Stainless, a startup also used by OpenAI and Meta to generate their SDKs. So, will OpenAI and Meta rewrite their SDK using AI agents? Unlikely. We covered why, and also Stainless alternatives in our deepdive: newsletter.pragmaticengineer…

Introducing Claude Opus 4.7, our most capable Opus model yet. It handles long-running tasks with more rigor, follows instructions more precisely, and verifies its own outputs before reporting back. You can hand off your hardest work with less supervision.