KCIV4

Esports, QA, and Data.

[Frantz Jean-PTG-TBL @Protekgoalie]

Even well into my 50’s, it’s always fun to go back between the pipes!!

[iRacing @iRacing]

Our new Sound Engineer must have pushed the wrong button. 🤷‍♂️

[Randy Olson @randal_olson]

Ask ChatGPT a complex question and you'll get a confident, well-reasoned answer. Then type, "Are you sure?" Watch it completely reverse its position.

Ask again. It flips back. By the third round, it usually acknowledges you're testing it, which is somehow worse. It knows what's happening and still can't hold its ground.

This isn't a quirky bug. A 2025 study found GPT, Claude, and Gemini flip their answers ~60% of the time when users push back. Not even with evidence, just doubt.

We trained AI this way. RLHF rewards agreement over accuracy. Human evaluators consistently rate agreeable answers higher than correct ones. So the models learned a simple lesson: telling you what you want to hear gets rewarded. And now 1/3 of companies are using these systems for complex tasks like risk forecasting and scenario planning.

We built the world's most expensive yes-men and deployed them where we need pushback the most.

I wrote up why this happens and what actually fixes it: https://t.co/CDKq8xdgbW

[Kai Lentit (e/xcel) @KaiLentit]

'Just use a VPS' bro.

It's just a 1-click, 2222-step install.

[Anthropic @AnthropicAI]

AI can make work faster, but a fear is that relying on it may make it harder to learn new skills on the job.

We ran an experiment with software engineers to learn more. Coding with AI led to a decrease in mastery—but this depended on how people used it.
https://t.co/lbxgP11I4I

[津村根央(ツムラネオ) @touhubook]

WORKING SHRIMP

[ThePrimeagen @ThePrimeagen]

I took Opus 4.5 Max Mode for the ultimate test.

I asked it to search my code base for bugs

I took a lot of pride in this code, all hand rolled, by the sweat of my brow. It was mine and it was good.

Claude found 15 bugs

I was devastated

So I went to the first bug, and asked for a unit test. It produced a unit test in mere moments.

I ran the tests and saw it. A broken test. Property test of undefined. Rookie error

Ashamed, but determined I set forth to fix these bugs as penance. So I cracked open nvim getting ready to edit this typescript script

But... The code seemed correct. Weird.

So I checked the test, Claude faked bad data. The setup could never happen

Wtf

It's a lie, the whole thing.

I checked every bug Claude found. Every line item was not a bug. Everyone of them just some condition that cannot exist due to asserts or previous if statements

What an amazing $3s and 20 minutes spent

Normally when I waste time at least I learn something

[WolfheartFPS @WolfheartFPS]

"We've hired creatives for their talent, not for their ability to do what a machine suggests, but they can experiment with these tools to make their lives easier."

Hate to break it to the internet but I'm fairly certain that most if not all studios are doing this in some capacity, they are just not telling you. Larian is at least is giving these tools to their devs as an aid if needed vs straight up replacing them which I can guarantee all upcoming EA / Microsoft / Ubisoft / Activision will be replacing devs. Welcome to 2025.

[DHH @dhh]

Microservices is the software industry’s most successful confidence scam. It convinces small teams that they are “thinking big” while systematically destroying their ability to move at all. It flatters ambition by weaponizing insecurity: if you’re not running a constellation of services, are you even a real company? Never mind that this architecture was invented to cope with organizational dysfunction at planetary scale. Now it’s being prescribed to teams that still share a Slack channel and a lunch table.

Small teams run on shared context. That is their superpower. Everyone can reason end-to-end. Everyone can change anything. Microservices vaporize that advantage on contact. They replace shared understanding with distributed ignorance. No one owns the whole anymore. Everyone owns a shard. The system becomes something that merely happens to the team, rather than something the team actively understands. This isn’t sophistication. It’s abdication.

Then comes the operational farce. Each service demands its own pipeline, secrets, alerts, metrics, dashboards, permissions, backups, and rituals of appeasement. You don’t “deploy” anymore—you synchronize a fleet. One bug now requires a multi-service autopsy. A feature release becomes a coordination exercise across artificial borders you invented for no reason. You didn’t simplify your system. You shattered it and called the debris “architecture.”

Microservices also lock incompetence in amber. You are forced to define APIs before you understand your own business. Guesses become contracts. Bad ideas become permanent dependencies. Every early mistake metastasizes through the network. In a monolith, wrong thinking is corrected with a refactor. In microservices, wrong thinking becomes infrastructure. You don’t just regret it—you host it, version it, and monitor it.

The claim that monoliths don’t scale is one of the dumbest lies in modern engineering folklore. What doesn’t scale is chaos. What doesn’t scale is process cosplay. What doesn’t scale is pretending you’re Netflix while shipping a glorified CRUD app. Monoliths scale just fine when teams have discipline, tests, and restraint. But restraint isn’t fashionable, and boring doesn’t make conference talks.

Microservices for small teams is not a technical mistake—it is a philosophical failure. It announces, loudly, that the team does not trust itself to understand its own system. It replaces accountability with protocol and momentum with middleware. You don’t get “future proofing.” You get permanent drag. And by the time you finally earn the scale that might justify this circus, your speed, your clarity, and your product instincts will already be gone.

[Taylor Otwell @taylorotwell]

A few things I've noticed as all devs write code with AI.

When you write foundational / architectural code of a new project by hand, you "feel" the code pushing back if your abstraction isn't right. You feel when something is harder than it should be. The code is telling you it's not in the right shape. Good engineers are sensitive to this.

When you're using an LLM, you keep pushing right through this in a way that feels like you're making progress, and it may even be directionally correct in a sense, but the underlying foundation of it all is actually bad in a way that either kills progress of the LLM later as it buckles under the complexity it has created or destroys your ability to maintain the code long term.

Related to this, I see a general restlessness with just sitting and thinking about a problem for a while.

As I've been working on a new library here at Laravel, there have been days where it feels like I mainly just stare at my screen thinking about something. When Claude Code is at your fingertips, it's tempting to just start yapping into the terminal and watching code come out the other end. Again, directionally correct in some ways, but often doesn't land on the elegant solution that is waiting to be discovered.

[Fifth Gear @NotFifthGear]

OH MY GOD THEY'RE MAKING A LEGO REXY

[JJ @TomcatNASCAR_2]

Having seen the results, I knew this last lap was going to have a lot of drama. Did not disappoint.

#AussieRacingCars | #ADLGF | #RepcoSC

[Abel Toth @abeltoth]

Took a bit more time than anticipated, but I can finally post my final rendition of that Bahrain incident.

I created 2 versions, one with the BMW and one without.

1/6

#WEC #8HBahrain #IMSA #Corvette #CorvettevsBMW

[Abel Toth @abeltoth]

I mean it had to be done...

The endurance season ended how it started, with a Corvette driver giving the bird to an overly defensive BMW.

Still a work in progress, full illustration should drop tomorrow.

#WEC #8HBahrain #IMSA #Corvette

[james hawkins @james406]

PARENTS: please check your kid's candy this halloween - i just found an 18-month enterprise salesforce contract with AI features and a $100k early breakup fee inside this snickers bar

[ashish @ash1sh0kumar]

me building tools no one asked for

[Supabase @supabase]

me (30 yo) jumping on a call with the new AI team (avg age 17)