Here’s my take: Like google, stackoverflow, and so on, AI is yet another tool in your toolbox. It can’t replace humans yet, and in fact it’s a ways off from that if you ask me. Not that it won’t eventually be able to do it, but it can’t yet. You said yourself, there are still elements that the AI just can’t do yet.

I like that I can say “hey AI, here’s what I need” and have it generate what I would consider a good framework to start from. It helps me eliminate the boring, time consuming stuff that I could easily do on my own. Your value comes in that other 20% now. The stuff that requires higher level understanding.

A big problem is that AI is creating technical debt in the form of deep understanding and expertise. You have the benefit of years of experience. You are the guru now.

Die Bart die

I hear that anti-geometrists are trying to get the pythagorean theorem banned in schools now.

Mine is Eric and the Dread Gazebo.

The exact two that I thought of. I honestly enjoyed Silent Hill more than I expected and even liked it more than Resident Evil.

This post on programmer humor is now funnier as a result of your analysis. Everything is funnier when it is 100% accurate.

I’m here to spread the good word about JSONC. It is the way and everyone should adopt it in place of JSON wherever possible.

How precise are your scissors?

It’s not a request, it’s a challenge.

It’ll take 20 hours. Unless it’s harder than I thought. Or it’s easier than I thought. Or it’s exactly as hard as I thought except there’s one little thing that I get stuck on for 5 hours.

We’re all NPC’s in some grand simulation running on a server in a warehouse long forgotten about and abandoned by the gods.

Comments can also be useful for explaining what the code is intended to do when debugging.

“Hey this function says it should return the number of apples, but looks like someone, not saying who, but someone had a brain fart and typed oranges in one variable. Who wrote this code anyway?”

-Last edited by JonEFive in 2021-

Past me sucks.

Strict vs loose equality has gotten me so many times, but I can sort of see why they did it. The problem you mention with integers 0 & 1 is a major annoyance though. Like it is fairly common to check whether a variable is populated by using if (variable) {} - if the variable happens to be an integer, and that integer happens to be 0, loose quality will reflect that as false.

But on the other side, there have been plenty of occasions where I’m expecting a boolean to come from somewhere and instead the data is passed as a text string. “true” == true but “true” !== true