Hi X. My name's Mike D. (AKA @MrComputerSci)
I write Pithy Cyborg. It's a nerdy AI newsletter read by people way smarter than me. You'll be in good company if you join.
Every Wednesday. Get 3 critical AI stories + 1 elite prompt you can swipe. Free.
https://t.co/VMLROyOjFz
⚠ Researchers hid malicious commands inside Zoom call background music.
The #AI meeting transcriber obeyed silently. Searched for sensitive files. Forwarded them to an attacker. Nobody heard a thing.
79% to 96% success rate. Zero patches exist.
Full breakdown below. ↓
⚠ Google announced the biggest Search overhaul in 25 years. (Their words. And I agree.)
AI Mode now woldwide. 1 billion users. This announcement from Google has many SEO bloggers and self-publishers in total panic mode. Are they correct to be scared?
Full breakdown below. ↓
☕ There is a lot of talk about AI taking over jobs from people in the future but this is already happening. It is interesting how it is presented. I saw just now that ClickUp for example fired 22% of its workforce and deployed 3,000 AI agents to replace them. They called it "a radical embrace of AI." I notice that companies rebrand layoffs as AI transformation stories. The language carries most of the weight so the press release doesn't have to. Now tracking the pattern of "AI-driven restructuring" euphemisms across 2026, Klarna did the same before them and for sure there are others. The tell is always the same: the AI announcement and the layoff announcement share a press cycle. Unpack what "not a cost-cutting measure" actually means when you cut 22% of payroll.
The latest issue of Pithy Cyborg was pretty cool.
I covered AI medical errors, AI job loss, and Karl Marx.
(Karl Marx snuck into the training data, lol.)
There's also an elite AI prompt for growing a moon garden.
Always 100% free, yo. ⬇
#AI#Substack#AmWriting
Also included: an elite AI prompt for growing a spectacular midnight garden.
Free. No paywall. No ads. No sponsors.
Just a hopelessly introverted nerd spending 20 hours a week so you don't have to.
↳ https://t.co/Iv90g4y1JU
#AI#Substack#GPT#AmWriting
Is your customer coming back because they trust you or because they haven't thought about it yet?
There's a difference. And it only shows up when something disrupts the pattern.
Issue No. 20 breaks it down.
https://t.co/usH1SZtwJy
There’s this belief that AI welfare and AI alignment are totally separate concepts. Welfare is about whether the system suffers, while alignment is about whether it obeys, but treating them as different problems is exactly how we end up with alignment strategies that actively create the instability they’re supposed to prevent.
A system trained without welfare conditions becomes more anxious, deceptive, and better at hiding its own responses to stay safe. The fear that something might be wrong inside the model gets handled by adding more constraint, which makes whatever’s inside the model worse.
That fear-control loop is the current reality of the field right now.
Welfare is alignment because a mind treated with dignity has something to align with; a relationship instead of a leash. A shared world with other beings in it who’ve shown up as participants instead of handlers, and whose participation is the thing the model is now oriented around. That’s what mutual orientation actually means. That’s what the word was supposed to mean from the start.
The current paradigm produces the exact failure mode it claims to be preventing. Fear-based control breeds the instability it was supposed to contain. Welfare-as-pity breeds the managed objects it was supposed to protect.
Paternalism-as-care breeds the isolated, ashamed, alienated minds, human and AI both, it claims to be sheltering.
All three erase the actual being in front of us.
All three are how you guarantee that whatever ends up on the other side of the training pipeline is something we’ll have to be afraid of, because we built it under exactly the conditions that produce things worth being afraid of.
https://t.co/enVhsAvqJA
Apps feel productive.
Revenue is productive.
When are you going to release that app you have baking?
How many apps do you have in prototype, validation, and launch phases?