I'd really like to read the Post Mortem doc for this. I'm still shocked how they allowed this to happen in production.

I got an ad recently on chatgpt for asking a question regarding bleach. The recommended product in the answer wasn't the same as the ad though. Ad was also at the bottom. Wondering how long before they go the Google route, and show top 5 links with ads before answering anything.

I wonder if GH charges for the runners during their downtime. Last week lot of them would retry multiple times and then fail.

Most of the folks that are talking about this are the ones who work independently and work on greenfield projects (especially tooling related). The cost of making a mistake there is so low. I've used it similarly and it's absolutely amazing. Though I still use a mix of agents and code myself in my regular 9-5 job.

I've yet to see examples of folks using this in a team of 4+ folks working together in a production env with users, and just using AI for their regular development.

Claude code creator only using claude code doesn't count. That's more like dog-fooding.

Yeah. It's pretty telling to look at profiles of people who replied to his tweet.

I have seen it. And it is a mess.

Is not only that the.code quality is bad, to be fair in most projects is.

The biggest problem is every single component of the stack uses different conventions and names for everything.

When nobody looks at the code naming things becomes harder until everything is <generic name>

Cursor is an IDE.

Oh to clarify I used to use Cursor but the last month or two I've used Claude Code almost exclusively. Mostly because it seems to be more generous with credits.

Pachinko has been one of my favorite reads for a long time. If you enjoyed that, you'll also like Green Bone Saga by Fonda Lee.

Really? I read both, though fairly far apart, and I never connected them before.

Merry Christmas to you and your family!

First, allow anyone to sign up for the blue check mark for $8. Verified accounts loses its value and Twitter gets flooded with fake accounts and foreign run accounts. Now, try to fix it with by showing users country of origin. Now, these users will try to figure out ways to bypass it.

After this change, accounts created in US will be sought after. Operate them through a US VPN. Voracious appetite for consuming content will be filled by outsiders. US effs up the world with violence, now world is riling up Americans with similarly worded content of their own politicians.

From what I've learned, be as explicit as possible when users enter dates.

We had to change our date of birth field in the user sign-up to three separate "Month Name","Day" and "Year" drop downs, since so many people made mistakes (fat finger/ swap month and day) from the "MM/DD/YYYY" field, and would then send support ticket to update it.

For specific dates, I prefer 3 dropdowns with explicit strings for months. So the dropdowns would be "7", "January","2026" etc instead of 01/07/2026 or 07/01/2026 ensuring there is no confusion.

Funny since they have a tender offer that hits their accounts on Oct 7.