@JannikWempe@bkase_@pidotdev@mitsuhiko https://t.co/ZUbgNKoGcL
https://t.co/CiQPIMQ0n9
https://t.co/KwbVcxeqI7
https://t.co/d2t4VOdORP
https://t.co/g4s2CxLDQt
Doesn't seem to be a good idea trying to force Claude Code to not use the system prompt. Because of Anthropic's classifier.
๐ฏ Co-sign.
For those of us who are mid- or late-career engineers and managers, the mandate shifted quite a while ago. We have decades of context on system design, software failures, architectural "taste", how to handle failures in distributed systems...
...but if you aren't modeling curiosity and pushing your teams and colleagues to build with AI - as well as sharing what you've discovered, attempting to inspire folks to experiment and to learn more - you're doing them a massive disservice.
๐๏ธ if your team is too busy doing their 'normal job' to experiment with AI, you're preparing them to be replaced
https://t.co/KTaIgFpvpK
In this post, I guess this's the last time I'll say it. AI use is no longer optional if you wish to be employed. What follows is advice for current employees and hiring managers on how to hire in 2026 to source AI-first candidates.
<<About a month into using Atlas internally as a team, Cloudflare published Codex. Same bones: governed standards, agent-consumed context at the point of work, a fixed status for every rule. We had been walking the same path...>>
- Atlas & Validation of the Design