Raise your hand if you have seen this story way too many times this year 🖐️
“I [AI expert] quit [AI company] because [terrifying AI thing]. Anyway, good luck everyone.”
At this point, whatever side of the AI doom debate you’re on, this has become a weird genre of tech news.
🗓️ Feb - Anthropic safety lead quits saying “the world is in peril”.
🗓️ Feb - OpenAI researcher quits as ChatGPT ads arrive.
🗓️ Mar - OpenAI robotics lead walks over military AI red lines.
🗓️ Jul - DeepMind researcher leaves after Google signs a military AI deal.
🗓️ Sep - now this 👇

Three days later, Anthropic’s CEO published a letter calling for slowing down frontier AI development so safety has time to catch up while OpenAI was pushing Congress for mandatory national safety rules.
And this isn’t completely coming out of nowhere. The recent Hugging Face incident (I wrote about it here) was a pretty real example of humans struggling to reconstruct what a large group of AI agents had actually done.
Which leaves normal people in a pretty strange position. How are you meant to form a sane opinion about any of this?
Most of us are trying to do our jobs, stay useful, and learn enough of whatever this is that five years from now we don’t look back and realise we sat the whole shift out.
Before ChatGPT, I spent years building a community around no-code. A lot of you actually followed me for that. I was obsessed with the same thing I am now: what can people like us suddenly do that we couldn’t do before? And this week, I think there’s a pretty good answer to that.
So today:
🔥 why software is starting to adapt to us, not the other way around
👀 what non-technical people are making at work
🧪 3 new ways to test AI on your work this week
THE FUTURE OF WORK WITH AI
This might be the AI story from this week that matters more to your actual job.
A developer spent a week vibe-coding an app then OpenAI shipped an update that basically made it obsolete.

At first this sounds like a pretty depressing advert for building anything with AI lol. But there’s another way to read it.
Software just became cheap enough to build in a week and disposable enough to replace the next one.
And I think that changes something much bigger than vibe coding. For most of our working lives, software has dictated how the work happens.
The CRM has these fields.
The dashboard works this way.
The tool doesn’t do that.
So…you work around it.
AI is starting to reverse that relationship. We’re seeing small versions of this inside 15 Days of AI all the time.
One person working in legal was frustrated by the world clocks available to her, so she made an editable one around the time zones she actually needed. Someone working in Workplace built a specialised Health & Safety assistant around information they were already responsible for. Others have been experimenting with contract review, spreadsheets, regulatory documents and stakeholder comms not because they woke up wanting to “build software”, but because they know where their own work is annoying better than anyone else does.
👉 Join the challenge with your team!
That’s why I think the whole everyone is a developer now framing is slightly wrong. You don’t need to become a software person. But knowing your own work deeply enough to say “this is stupid, it should work like this instead” is becoming a much more valuable skill.
Ready to build real AI capability
Get weekly insights on adoption, team rituals, and practical workflows — straight to your inbox.



