1 point

Basic rule if someone claims X magically solves a problem they don’t follow X and are a huge generator of the problem.

For example people who claim they don’t need to write comments because they write self documenting code are the people that use variable names x1,x2,y, etc…

Similarly anyone you meet claiming Test Driven Development means they have better tests will write code with appalling code coverage and epically bad tests.

permalink
report
reply
1 point

10 months? More like a weekend for me.

permalink
report
reply
-1 points

The reason there are no comments in the code? Written by ChatGPT.

permalink
report
reply
3 points

It appears you haven’t used chat gpt for coding help.

permalink
report
parent
reply
1 point

ChatGPT actually puts a lot of comments in, especially when minor modifications are needed to make something work.

permalink
report
parent
reply
9 points

This is Bill.

Bill doesn’t need to minify his code, he names things using a single character even in compiled languages.

Bill is a heckin chad who can guess what the code does merely by looking at types and control flow.

Be like Bill

permalink
report
reply
1 point
*

I’m no heckin chad like bill ima soyjak :(

permalink
report
parent
reply
1 point

Is the Greek question mark a legal identifier for variable names?

permalink
report
parent
reply
2 points

I started coding with TurboBasic. My favorite thing about TB was that you could have variable names of any length but the compiler only used the first two letters - and case insensitive at that. So “Douchebag” and “doorknocker” looked like different variables but were actually the same thing.

permalink
report
parent
reply

I don’t care how much you think your code is readable, plain text comments are readable by everyone no matter the proficiency in the programming language used. That alone can make a huge difference when you’re just trying to understand how someone handled a situation.

permalink
report
reply
1 point

Then someone needs to change something about the code and doesn’t bother updating the comment. Now you still have uncommented code but with a comment that confuses instead of helping.

permalink
report
parent
reply

IMHO the issue in this situation is not the comment but that the person updating the code didn’t do his job properly which shouldn’t be an excuse not to do it from the start.

permalink
report
parent
reply
5 points

Comments explain why, not what. Any comments that explain what a section of code is doing would probably be better off as separated methods.

Apart from basic documentation comments, like JavaDoc or C#'s XML documentation comments.

permalink
report
parent
reply

There’s nothing limiting what a comment should be as far as I know.

As an example of what I mean, I’ve seen in a 10k+ lines python code a few lines of bit manipulation. There was a comment explaining what those lines did and why. They didn’t expect everyone to be proficient in bit manipulation but it made it so that anyone could understand anyway.

permalink
report
parent
reply
2 points

There’s nothing limiting what a comment should be as far as I know.

Nothing technical, sure. Just good coding practices.

permalink
report
parent
reply
2 points

There’s nothing keeping the comments up to date with the code. Comments should be sparse and only on sections that aren’t obvious why they’re being done

permalink
report
parent
reply

Programmer Humor

!programmer_humor@programming.dev

Create post

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

  • Keep content in english
  • No advertisements
  • Posts must be related to programming or programmer topics

Community stats

  • 7.2K

    Monthly active users

  • 954

    Posts

  • 36K

    Comments