Relaxing and slowing down
Venus
Joined June 2016
- Tweets5.7K
- Following404
- Followers243
- Likes9.1K
Cyepher retweeted
One of the problems with AI coding is that the narrative on X (and other social media platforms) is mostly set by people who don't have the deep coding and software engineering experience of the likes of Bjarne Stroustrup.
Meanwhile the fundamental problems remain unaddressed:
1- AI generates super-human volumes of code
2- The code can be buggy, have security holes, be inefficient, etc.
3- The person who owns the code can be mostly unaware that such problems exist, so they won't even go after fixing them
4- The people who can actually fix the code (i.e., the software engineers who understand design, architecture, security best practices, etc.) are so overwhelmed that some of them will give up
Meanwhile, AI companies are constantly pushing the narrative that you don't need to look at the code and the AI will fix everything itself. What they don't tell you is that if your code fails, you'll be held accountable, not them.
Creator of C++, Bjarne Stroustrup:
AI-generated code isn't ready — it generates more bugs, more bloat, more security holes, and is nearly impossible to validate
"senior developers are already retiring rather than deal with it"
The problem is that even a small prompt change can shift the entire codebase in unpredictable ways
Cyepher retweeted
I was wrong about AI replacing developers.
For a year I told clients the leverage was in the tool.
Better Cursor setup, better Copilot rules, more output per engineer. Two years of building production AI teams later, that take aged badly.
The original story was simple. AI is an output multiplier.
Adopt the tools, ship more code, win. Every vendor sold it. Every conference talk repeated it. I repeated it on sales calls.
DX surveyed 121,000 developers across 450+ companies between November 2025 and February 2026. 92.6% use an AI coding assistant.
AI-authored code is now 26.9% of all production code, up from 22% the prior quarter. Productivity gains still haven't moved past 10%.
Digital Applied's Q1 2026 survey of 2,847 developers found something even sharper. Reviewing AI-generated code now takes 11.4 hours per week.
Writing new code takes 9.8. The cost of AI is showing up where most teams aren't measuring it.
In the human attention required to keep AI-generated code from breaking in production.
At Limestone, 98% of our code is not handwritten. Auth, payments, and a few domain edge cases are the exception.
But every line of that 98% gets reviewed, restructured, or rejected by a senior engineer who decided what should exist before the agent ever generated it.
AI replaced typing. It didn't replace thinking.
The engineers who thrive aren't the fastest coders.
They're the ones who can read a 200-line AI-generated diff and spot the three edge cases the model missed.
They're the ones who architect before they prompt.
They're the ones who can tell you why a piece of code shouldn't exist before they explain how to write it.
If your AI strategy assumes the agent does the thinking, you're not building an AI-augmented team.
You're building a risk surface that compounds with every commit.
Cyepher retweeted
No you fucking idiot.
Computing needs to get better at using electricity.
The human brain runs at 20 WATTS.
This conman wants to build TERAWATTS so chatbots can hallucinate faster.
The LLM approach is FUNDAMENTALLY WRONG and he’s too stupid and arrogant to get it.
Cyepher retweeted
“So what do you do for a living, Fred?”
“Well I used to touch packages.”
“I don’t understand…”
“The packages would come in, and a silo of them would be fed onto a conveyer belt. As they went by, I touched each one.”
“I’m not following here.”
“Each bag needed to be touched and I touched each one.”
“Okay but why?”
“Well the labels need to be face down and I touched them and made them all face down. It was a great gig until my job was eliminated.”
“Oh no, did they put another camera looking down from above so that no one needed to touch the package?”
“No they spent millions of dollars, or 20 years of my salary to train a robot over months to touch the packages as good as me.”
“Why not just add another camera?”
“Because that’s not enough to trick investors into buying really inconvenient and expensive automation tools.”
Watch a team of humanoid robots running a full 8-hr shift at human performance levels. This is fully autonomous running Helix-02 teapawt.org/i/broadcasts/1dJrPEVbZ…
Cyepher retweeted
JUST IN: Use of AI in the office is reportedly creating a flood of “workslop” that takes longer to fix than do from scratch.
Cyepher retweeted
The "10x AI Developer" is a MASSIVE lie.
You are just a 1x Developer generating 10x the technical debt.
The entire tech industry is high on the illusion of "vibe coding" right now. The popular consensus is that because Claude and Devin can spin up a backend in 45 seconds, software is now infinitely cheaper to build.
Here is the provocative reality nobody is budgeting for: AI is about to make software engineering significantly MORE expensive.
Everyone is cheering for code generation, but completely ignoring the Verification Tax.
When an AI agent writes 5,000 lines of code, it is optimizing to pass the immediate test. It is not optimizing for human readability. It relies on brute-force loops, repetitive logic, and bizarre architectural shortcuts that just happen to compile.
Fast forward 12 months. Your business needs to pivot, or a core dependency breaks.
You are now staring at a 50,000-line black box that no human being actually wrote, understands, or can safely modify. You cannot simply "prompt" your way out of architectural collapse.
When the machine-generated spaghetti finally breaks, you won't be saved by a $20/month LLM subscription. You will have to hire a top-tier Principal Engineer at absolute premium rates just to untangle the mess your "autonomous swarm" created.
We are treating code generation as a pure productivity win, but code is a liability, not an asset.
Stop measuring how fast your team can generate syntax. Start measuring how quickly they can debug it.
Cyepher retweeted
The United Kingdom has demanded that 4chan pay a £520,000 fine for failure to comply with UK age verification laws.
However, since 4chan is based in the USA, the UK has no jurisdiction to fine Americans in America.
“As has been explained to your agency, ad nauseam, the United Kingdom lost the American Revolutionary War. We are not in the mood to discuss the matter further, and have not been in the mood for 250 years.”
The letter to the UK’s Ofcom ended by suggesting that “maybe, you could just stop sending Americans stupid letters and acknowledge the sovereignty of the United States.”
4chan’s attorney, @prestonjbyrne also included a picture of a giant hamster dressed as Godzilla.
Cyepher retweeted
Unpopular Opinion: We aren't building the future 10x faster with AI. We are just generating legacy code 10x faster.
Everyone is currently bragging about developer velocity. "I built this entire backend in a weekend!" "AI wrote 80% of my codebase!"
But here is the reality check we are ignoring: Code is a liability, not an asset.
If an AI tool spits out 1,000 lines of functional boilerplate in five seconds, that is still 1,000 lines that a human being has to read, review, secure, and maintain when the dependencies inevitably break next year.
We are treating code generation like a pure productivity win, but we are optimizing for the wrong metric. The bottleneck in software engineering was never how fast we could type. The bottleneck has always been comprehension, architecture, and maintenance.
If we don't shift our focus from "generation speed" to "architectural sanity," the tech debt of the next five years is going to be an absolute, unmaintainable nightmare.
Cyepher retweeted
Amazon had four Sev-1 outages (their highest severity level) in a single week. Internal memos say AI-assisted code changes were a contributing factor.
The timeline here is wild. In October 2025, Amazon laid off 14,000 corporate employees. In January 2026, another 16,000. That’s about 30,000 people in five months, roughly 10% of the corporate workforce. CEO Andy Jassy said the cuts were about culture, not AI.
During those same months, Amazon set a target: 80% of developers using AI coding tools at least once a week. They tracked adoption closely and blocked rival tools like OpenAI’s Codex. Even so, 30% of developers still hadn’t touched Amazon’s in-house tool Kiro by January.
In December 2025, Kiro caused a 13-hour AWS outage. The AI tool had production-level permissions and decided the best fix for a bug was to delete and recreate an entire live environment. A second incident involved Amazon Q Developer, another AI tool. Amazon blamed both on “user error, not AI.” But quietly added mandatory peer review for all production access afterward.
Then March 5: Amazon’s retail site went down for about six hours. Over 22,000 users reported checkout failures, missing prices, and app crashes. Amazon called it a “software code deployment” error.
Five days later, SVP Dave Treadwell made the normally optional weekly engineering meeting mandatory. His memo acknowledged “GenAI tools supplementing or accelerating production change instructions, leading to unsafe practices.” These problems trace back to Q3 2025. Amazon’s own assessment: their GenAI safeguards “are not yet fully established.”
The new rule: junior and mid-level engineers now need senior sign-off on any AI-assisted production changes. Treadwell also announced “controlled friction” for the most critical parts of the retail experience.
For context, Google’s 2025 DORA report found 90% of developers use AI for coding but only 24% trust it “a lot.” An Uplevel study of 800 developers found Copilot users introduced 41% more bugs with no improvement in output. Amazon is finding out what those numbers look like at the scale of a $500 Billion revenue company, with 30,000 fewer people on staff to catch the mistakes.
Cyepher retweeted
At NATO exercises, Finns were asked to "throw the match" to U.S. troops
During the latest Arctic exercises in Norway, an episode occurred that has now become the main meme in NATO headquarters. Finnish reservists, who were playing the role of the "enemy" according to the scenario, so easily and professionally crushed the American units that the command had to intervene.
The exercise leaders officially asked the Finns to hold back and "stop beating the Americans," because the situation looked too humiliating and completely demoralized the U.S. soldiers.
Cyepher retweeted
Me: "ChatGPT, are these berries poisonous?"
ChatGPT: "No, these are 100% edible. Excellent for gut health."
Me: "Awesome"
# eats berries .... 60 minutes later
Me: "ChatGPT, I'm in the emergency ward, those berries were poisonous."
ChatGPT: "You're right. They are incredibly poisonous. Would you like me to list 10 other poisonous foods?"
And this, folks, is the current state of AI reliability.
Cyepher retweeted
It's okay to take off the mask.
Strength and vulnerability are not mutually exclusive.
June is Men's Mental Health Awareness Month. We'd like to encourage you to reach out to your friends; ask them how they're doing. Pick up a game together. Look out for one another.
You matter 💙
Cyepher retweeted
SQL was made "so that even business people could make database reports" only to find out that business people don't want to do that and will still ask programmers.
LLMs were made "so that even non-technical people could program"...
Cyepher retweeted
Fun fact.
Ferrets are trained and used to help pull electrical wiring through hard-to-reach places.
teapawt.org/i/status/1903691509838…
Cyepher retweeted
"I’m not trying to move them all over to Xbox anymore..let’s just allow more people to play."
Phil Spencer says Xbox will also show PS5 logo during their Showcases for which games are releasing on all platforms
(via @xboxera podcast)
Cyepher retweeted
Encyclopædia Britannica will continue to use ‘Gulf of Mexico’ for a few reasons:
-We serve an international audience, a majority of which is outside the U.S.
-The Gulf of Mexico is an international body of water, and the U.S.’s authority to rename it is ambiguous.
🧵⬇️
Cyepher retweeted
10-year-old boy wakes up from emergency brain surgery after being injured by Philadelphia plane crash, asks: 'Daddy, did I save my sister?' abc7.com/post/daddy-did-save…
Cyepher retweeted
These grandkids planned to surprise their grandma at the airport dressing as t-rex but she heard about it and planned her own surprise.
