The agents are now writing 90% of the code, which humans then throw away.

But actually this phenomenon of writing one to throw away is going to be amazing for what we can explore.

For me Tesla's brand is irreparably damaged.

That's worth accounting for - I'm likely not alone.

Can you point me to where to read things perfectly polished by Opus?

I'll give them to Opus to show it how not to suck at writing.

Sometimes you have a goal & clarity about what you want; others you're just exploring.

Just as non-assisted work: an undisciplined mind will wander. But when there's also an assistant, you're prone to having the wandering done for you.

"Where's the popular front?"

"He's over there."

https://youtube.com/watch?v=WboggjN_G-4

Fastmail is great, and has fantastic migration tools. I have all 131,000+ emails in Fastmail, nothing left in gmail, I don't miss it.

And the search works and is precise.

Took me months to decide to migrate (even though its on my own domain) but I haven't looked back.

Worth mentioning CI is not part of production outages!

You should never fix an incident by deploying another fix as it risks making things worse especially while everyone is panicking. Better to roll back - and spread non-backwards compatible work across multiple deploys that each are backwards compatible - always giving yourself a known good state to roll back to.

Rollback should not done be via your CI either! Set up some low dependency thing - a separate tool or script or system.

Once you've rolled back and got the system stable, then produced a fix at your leisure, that's when CI comes back into the picture :)

Having spent too many years in CI/CD I'd agree but there is an even better solution; decouple deployments from releases. Make it possible to deploy without releasing, and release without deploying. (An implementation of this could be, for example: feature flags.)

I prefer the term "corporate autoscaling".

Dear creator: you didn't ship the first draft of your code - why did you ship the first draft of your README??

because claude ships these verbose READMEs with its 'honest' takes and justifications for the naming. Its goal is to prime the next Agent that reads it, not you, human

we need a new HUMANS.md to replace the readme