Programmer Humor

I was part of project that scoffed at the idea documenting code. Comments were also few and far between. In retrospective, it really seemed like they wanted to give that elitist feel because everything reeked of wanting to keep things under wraps despite everything being done out in the freakin' open.

This is the dram. Since the entire codebase is shit, you basically have to rewrite it basically in its entirety.

Which means you can do it with an actual good design.

And if you mess up on something, you have a working version you can consult.

Hey! This was my first real job. Is Matlab code written by physicists who just recently learned programming.

You got 3 letters?! Luck!

I worked at a japanese company whose engineers we're former NTT developers. Copypasta (i.e. not using functions), inefficient algos, single-letter var names, remote code execution from code as root, etc. good times!

Allow me to introduce a shit ton of jQuery into all the jsp files you got.

I can live without documentation and comments, but then you've got to write really well-structured, self-documenting code. Which means long variable names (or better: local constants) that describe exactly what's in them, and function names that describe clearly what the function is for, and readable code that shows what it does.

But perhaps expecting that kind of discipline from people who lack the discipline to write documentation, was not entirely realistic.

Honest question: would an LLM be able to write useful comments in code like this?

The only experience I have like this is when I wanted to see how the ARMA Life mod was doing certain things, but it was programmed by like 20 different people in 3 different languages. Most of it was in German and French.

It was easier to just to find my own way of doing what I wanted to do.

The next row would be "boss fires you thinking Claude can maintain the codebase."