I thought that was kind of how the hard sciences work already?

My grad school friend who was a physicist would write his talk just before his conferences, and then submit the paper later. My experience in CS was totally backwards from that.

Find-then-patch only works if you can fix the bugs quicker than you’re creating new ones.

Some orgs will be able to do this, some won’t.

"Find me vulnerabilities in this PR."

You’re conveniently ignoring the Olympic boxing champion from 2024 who beat the absolute shit out of the female competitors.

Are you talking about Imane Khelif? The woman who was born a woman, competed her whole life as a woman and is still last time I checked, a woman?

A woman with an SRY gene undergoing treatment to reduce testosterone levels to typical female level. https://nypost.com/2026/02/06/sports/imane-khelif-opens-up-o...

Or maybe this is like fondly remembering the busted economy car that you drove around with your friends? I have my first 386DX sitting on my desk right now and it looks exactly like the top left of that photo.

The hot car that we all lusted after was maybe something like a SGI Indy or an O2.

You’re not wrong, but you probably could have built the thing with Claude in the time it took you to write this comment.

The closest thing we have is, in security / privacy / cryptography, you can write "attack" papers.

It's not perfect. You don't get any credit unless you can demonstrate a substantial break of the prior work. But it's better than in a lot of other fields.

Several people have tried over the years. We all failed, because it doesn’t work.

The economics don’t work because no one is willing to pay.

The network effect doesn’t exist, because real people don’t post enough to get the flywheel started.

All the dark patterns exist because that is what users reward.

Sucks but it’s true.

Very likely they got the causality backwards. Every time there’s a big war, technology advances because governments pour resources into it.

Just burn the tokens. It’s an upfront cost that you pay once at the beginning of a project, or on a smaller scale at the beginning of a major feature.

For context, I’ve built about 15k loc since Christmas on the $20 plan, plus $18 of extra usage. Since this is a side project, I only hit the limits once or twice per week.

It’s really not. For anything substantial, the things that you do to manage an LLM are the same things that you should be doing to manage a team of human devs, even if the team is just yourself.

Documentation. Comments. Writing a plan and/or a spec before you begin coding. Being smart with git commits and branches.