Perhaps I'm speaking out of depth because I haven't done a lot of Golang, but I've always thought of it as a systems language first, which means by necessity you have you to handle lower level problems yourself. I'm sure there's plenty of libraries that paper over this - but the philosophy of the languages themselves is different. Javascript was designed to solve CRUD like interfaces/problems quite well.

Maybe this is just an outdated argument though that isn't really relevant with modern golang/rust though.

Sometimes I'll go down a rabbit hole of clicking AI generated videos just because my curiosity is piqued, and then I'll be stuck getting that slop fed to me for the next week. I have to make a mental note to actively disengage with it as quickly as possible to tip the algo in the other direction.

A podcast with guests is an interview. Interviewing is a skill. The difference between a good and bad interviewer is night and day.

It’s been fun to come back to, most of the code I wrote still drives the business (it’s just far outdated).

I was pretty early on in my career when I wrote it, so seeing my mistakes and all the potential areas to improve has been very interesting. It’s like buying back your old high school Camaro that you used to wrench on.

I get it in the context of driverless but find it nothing but annoying as a driver.