I think this is just a picky optimization.

The first one runs the constructor to instantiate a new string, then gets its class (which is presumably a static property anyway). The second doesn’t have to run any constructor and just grabs the static class name from the type.

Maybe there’s more implementation nuance here but it seems like an opinionated rule that has zero effect on performance unless that code is being called thousands of times every second. And even then the compiler probably optimizes them to the same code anyway.

Wasn’t it Visual SourceSafe or something like that?

God, what a revolution it was when subversion came along and we didn’t have to take turns checking out a file to have exclusive write access.

This happened to me once and I completely overthought it.

In my case, I removed the PCB from the drive and took a close look and saw a single scorched IC that I figured was the problem. I think it was a voltage regulator or something like that.

So I bought a scrap drive and tried to transplant the PCB onto my dead drive, but of course that wouldn’t be able to read my old data.

So took it into a local electronics repair shop and asked if he’d be able to make it work.

He took one look at the damaged PCB, pushed the scrap one back at me and said “yeah I’ll just replace this part.”

40 bucks later I had a working drive again and was able to rescue the data.

Elon’s shock and fury about the database key sounds like he got a report from an out-of-breath 20 year old DOGE kid who thinks they’re hot shit and discovered some massive flaw.

Elon also seems like the kind of person that believes a database schema is all that’s needed to govern a population.

Warnings? We’ll come back and address those later. Maybe once we’re feature complete. Or maybe shortly after that.

A full stack developer is either a back end developer that has no business writing front end code but does it anyway, or they’re a front end developer that has no business writing back end code but does it anyway.

Or they’re perfectly capable of doing both because they’re at a startup that’s years away from running at scale or having to worry about performance and security.

It’s a little worrisome, actually. Professionally written software still needs a human to verify things are correct, consistent, and safe, but the tasks we used to foist off on more junior developers are being increasingly done by AI.

Part of that is fine - offloading minor documentation updates and “trivial” tasks to AI is easy to do and review while remaining productive. But it comes at the expense of the next generation of junior developers being deprived of tasks that are valuable for them to gain experience to work towards a more senior level.

If companies lean too hard into that, we’re going to have serious problems when this generation of developers starts retiring and the next generation is understaffed, underpopulated, and probably underpaid.