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

Management: “We’re only going to hire ‘full stack’ devs from now on.”

Also Management: “Why is this page taking 37 seconds to load?”

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.

You get a lawn and white New Balances at 30. At 40 you get nearsightedness and additional back pain.

“jubilationtcornpone is a great dev. He closes more tickets than anyone.”

QA: “Yeah, Hi. Can you look at this defect ticket?”

Reading ticket details…

Me: “Let me guess. Is [whatshisname] responsible for this?”

QA: “Yeah.”

Me: “Get him to fix it.”

QA: “I tried. Like four times.”

Me: Sigh “I’ll take care of it.”

QA: “Thank you!”

“We’re gonna make a fully functioning e-commerce website with only this WYSIWYG site builder. See? No need to hire any devs!”

Several months later…

“Well that was a complete waste of time.”

Remember when “The Cloud” was going to put everyone in IT out of a job?

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