Programmer Humor

AI is corpo_slob theft. AI is used to kill kids. AI is a exponential decay feedback loop deskilling method brought to by the capitalist class. It will be used to lower wages. It will create security traps where the corpos can gain... ohhh the drama!!! We need regulation META cries....The lady doth protest too much, methinks, dolla dolla bills ya'll. It will be used to spy on you and take away your free speech. It is a Poisonous cup of pee. We need more than cheese buger farts and violence. I want to live in a real culture not the techno bro hoedown. After the magic trick, they will pull the rug and you will be left with nothing, without a job. Lower the standards, corner the domestic market, lose the war and claim victory... seems fimilar too me. We are past the point of regulation. Wait til you see the effects of digital ID. They got black sites in the USA were the keep kids in cages... the tech bro and his slave trackers, thats how they get you. Bugs everywhere sold to you as tools and as toys. Language is Language and it changes over time. Empires are built on the ashes of others. Innovation and creation is communication and cooperation. The kings love to pick their fruit of the peasants labor as the knights protect the castles walls. We are entering stagflation and corpotechbro fuedalism. Slop be ass far ass the eye can see. The war in ukraine and the genocide in gaza are connected. The iceburg not fully revealed... the capitalist class is a trashy family... but they stick together and run their games. Look up 7 mountain mandate... now thats some Manchurian candidate

A lot of the arguments people use against vibe coding sounds a lot like "You shouldn't use a high-level programming language unless you understand the assembly it compiles to."

I know I'm gonna get flamed for this, but here goes.

I have vibe coded a system at work that has enabled me to deliver value in a fraction of the time I expected. My verification steps have been around whether it does the things I told it I wanted it to do. I'm not maintaining the syntax and I'm not expecting anyone else to. Ever.

That said, our teams that deliver products that touch customer data or financial records....they shouldnt (and dont) engineer this way. The tech isnt there (yet).

Let the flaming commence.

I think I know who did that meme. We had a programmer by that name who did just that.

So... Just like any other legacy system you inherit.

actually, be exactly like bill. boss wants slop, boss gets slop.

boss wants incomprehensible buggy code? that's right, boss gets incomprehensible buggy code.

I've seen the comments AI adds and yeah... No.... It's often pointing out the obvious or even in some cases just misleading.

Does Bill have the flaming frenzy within?

Asking an LLM to add comments is actually pretty much the worst thing you can do. Comments aren't meant to be documentation and LLMs have a habit of writing documentation in the comments. Documentation is supposed to be in the documentation, not in the code. LLMs are often trained on things like tutorials, where super obvious statements are commented to allow people to learn and follow along. In actual code you absolutely do not do this, obvious statements should be obvious by themselves. At best it's extra work to read and maintain the comments for obvious statements, at worst they are incorrect and misleading. I've worked on systems where the comments and the code weren't in line with each other and it was a continual guess if the comment is the way it was supposed to work, or if the code is correct and the comment wrong.

So when do you actually add comments? That's actually very hard, something people argue about all the time and a bit of an art form to get right. For example if I have some sort of complex calculation, but it's based on a well known algorithm, I might comment the name of that algorithm. That way I can recognize it myself right away and someone that doesn't know it can look it up right away. Another good indicator for comments are magic numbers. It's often smart to put these in constants, so you can at least name them, but a small little comment to indicate why it's there and the source can be nice. Or when there is a calculation and there's a +1 for example in there somewhere, one might ask why the +1, then a little comment is nice to explain why.

Comments should also serve like a spidey sense for developers. Whenever you are writing comments or have the urge to add some comments somewhere, it might be an indicator the code is messy and needs to be refactored. Comments should be short and to the point, whenever you start writing sentences, either start writing documentation or look at the code why it's required to explain so much and how to fix that.

Another good use for comments is to warn away instincts for future devs. For example in a system I worked on there is a large amount of code that seems like it's duplicate. So a new dev might look at it and see a good place to start refactoring and remove the duplicated code. However the duplication was intentional for performance reasons, so a little comment saying the dupe is intentional is a good idea.

I've also seen comments used to describe function signatures, although most modern languages have official ways of doing that these days. These also might border on documentation, so I'd be careful with that.

LLMs also have a habit of writing down responses to prompts in the comments. For example the LLM might have written some code, you say: Hey that's wrong, we shouldn't set x to y, we should set it to z. And the LLM writes a comment like // X now set to Z as requested. These kinds of comments make no sense to people reading the code in the future.

Keep in mind comments are there to make it easier for the next guy to work on the code, and often that next guy is you. So getting it right is important and hard, but very much worth while. What I like to do is write code one day and then go back and read it the next day or a few days later. And not the commit, with the diff and the description, the actual files beginning to end. When I think something is weird or stands out, I'll go back and edit the code and perhaps add comments.

IMHO LLMs are terrible at writing code, it's often full of mistakes and oversights, but one of the worst parts is the comments. I can tell code was AI generated right away by the comments and those comments being present are a good indicator the "dev" didn't bother to actually read and correct the code.

Bill doesn't understand liability clauses in contracts when he sells his vibe coded shit as a SaaS platform and gets popped because AI forgot about SQL injection.