And a pleasure to make yours. I loved the music in Tchia.

I suspect I would, yes. I would like some music.

(Note: I have not, in fact, won $100 million. I have not even won $10.)

You know it, friend.

Mild suggestion: cream cheese and bacon bits. Make jalapeño poppers without the frying.

Or make a batter and fry them if you’re ambitious.

One thing more people should do is let themselves explore if they're trans.

I did it. Never went past the brain thinking about it stage because I realized nope, I felt real comfortable as a dude. Name felt okay. Body felt okay.

No harm done.

It would help everybody all the way around.

Yeah well that’s all my suggestions too.

another typo. People in live ops chats DON'T know what they're talking about...

And I mean, the engineers who own the product usually do, and are trying to diagnose as fast as they can. It's the product managers trying to get the serve back up "as soon as possible" (as if the engineers weren't.)

Man, what a typo. The "version version". It's like chai tea.

Standing up the FIRST version....

Anyway, it was a good experiment, and I may keep developing the project, and I learned a lot. Thanks for reading.

Spicy autocomplete does NOT understand issues.

My best success was, after explaining what I thought was an issue going "okay, repeat it back to me so I can make sure your numbers can represent this"

Often times it couldn't. That's when I knew it was dumb to try its fix.

Claude's "solutions" are like that.

"This code failed to work because it timed out. I'll go raise the timeout..."

"This code failed to work because it can't process the standard name. I'll go add the non-standard name to the sender..."

"This code failed because zeroconf deadlocked the http..."

Them: No, I mean the data _in_ the database.

Me: You mean like try to figure out who's gonna log in and...

Them: No. Caches are fast. Just cache the database.

Me:.... like the whole database?

Them: Yeah.

Which, to my surprise, it got about 70% of the time (I kept track.)

But it's solutions to those problems? Oh my.

It's like the time somebody on a live ops call suggested I deal with a problem on WoW by "caching the database."

Me: The proxy already caches the live data....

Also, I'm pretty convinced some of the training data is live ops chats...

...because it's diagnoses read like live ops chats...

the problem is the people in live ops chat know what they're talking about.

A lot of times Claude would read a log, confidently identify the problem...

and Claude utterly fell apart. Anything other than the simplest change went off into tangents or added code that didn't need to be there.

Lots and lots of time debugging stupid shit, like Claude liking to use Unicode characters in log lines when some old tools (and Windows) don't deal well.

Standing up the version version of each step of Cedalion went incredibly quickly, and I went from nothing to almost fully functional pipeline in an evening.

That was crazy.

Then I started trying to improve it....

A few follow-up points after using Claude on a personal project in a language I am less familiar with.

I understand why people think "vibe" coding will become a thing, and why I'm utterly convinced it won't.