After the next partition of Poland @FaXistic will be in charge of Wroclaw.
slug life retweeted
A little more than 24 hours left on the Planet Shark miniature Kickstarter if your interested.
kickstarter.com/projects/daf…
Also little shark bakery
In America having a functional federal ID system worthy of the 20th century is forbidden by law.
Replying to @ripplebrain
To save water for datacenters all tap water will now have 20% ethanol.
Monaco F1 shows that luxury can become a public service. When exclusion outweighs experience to such a degree that people should be thankful for being kept out.
The solution is a full career path for code reviewers and curators.
Insread of today's rugpull where people spend years writing code and when they get good their job suddenly changes to reading code.
AI code is more dangerous than bad code.
A junior's mistakes are obvious. The naming is off, the style is messy, you see the shortcut from a mile away.
You know exactly where to look. Takes 5 minutes in review.
AI-generated code is clean, idiomatic, properly styled, and confidently wrong. The logic fails at the architectural level while looking production-ready on the surface. That's not a small difference. That's a different kind of problem.
22,000 developers tracked over 2 years. Bugs per developer up 54%. Review time up 200%. 31% of PRs now merge with zero review at all.
Not insufficient review. Zero.
And 25% of pull requests are now reviewed by other AI agents because teams figured they'd automate their way out of the bottleneck. It's not working.
You can't solve "code that fools humans" by adding more automation.
The bottleneck is senior engineers. They're the only ones reading past the syntax. And nobody's asking what happens when their review queue triples while leadership celebrates velocity metrics.
I wonder how many engineers are actually thinking before they press enter.













