Also losses. Gotta get that sweet, sweet too-big-to-fail bailout money.

One of the best bosses I ever had was an electronics engineer (I’m software). There are a lot of shared concepts between engineering disciplines. I enjoyed working with hardware engineers and getting to see how they approach problems.

It’s more like:

Start with some AI generated code.

AI code fails to compile immediately, if you’re lucky.

If not, spend three days trying to find some really stupid bug.

Delete the AI code and write it yourself.

This is a Repost

Big Beautiful Code

Senator Tom Cotton

Ah. Yeah, that tracks.

There comes a point, somewhere late in the evening after my ADHD meds have worn off, where it’s more productive to not do any coding. If I do, I’m just going to end up throwing most of it out tomorrow because it’s a bunch of bug littered spaghetti.

Unfortunately, I also solve most of my big problems when I’m not staring at a screen. After which I have to resist the temptation to go work on it so I don’t make a big mess. It’s some kind of cruel irony.

“Full Stack Dev” AKA Backend Dev who knows just enough about CSS to be dangerous.