Yes it is. Look at the eyes on the ducks. Also the guy's hands and nose. Dead giveaways.

I wouldn't be surprised if the whole meme was. What on earth does the picture have to do with the text lol

Why tf does someone need ai to make memes?! Jesus Christ...

For my current job we've all agreed to take the approach of not writing comments that say what the code does, but why you did something the way you did. Probably about 90% of our code is uncommented because it just doesn't need to be, but every once in a while you have to do something out of the ordinary to get the desired behavior, and explaining why you made the weird decision you did is infinitely more helpful.

I strongly disagree with the comments. "The code is the documentation" was a dumb joke about being to lazy to write documentation, not a best practices guideline.

Proper naming is good, but there are a lot of issues with not commenting code. Obviously it's dumb to comment every line, but it's really useful to comment functions/methods, because otherwise you never know if something's a bug or a non-obvious feature. Comments act as a parity check to the code, since they tell you what the dev who wrote the code wanted the code to do.

Also, everone thinks they write good, clean and obvious code. Hardly anyone purpously writes bad, hacky code. Yet if you look at code you wrote a year ago, or code someone else on your team wrote, it's full of non-obvious hacks. That means, people constantly misjudge the obviousnes of their code. Comments should be put on anything that could maybe be non-obvious.

And putting documentation of the code anywhere else than in a comment (e.g. Confluence) is a total waste of time (unless you put a link to the specific page of the documentation in a comment in the code), because documentation that you don't directly see without effort will not be found and not be read.

The problem here is that every junior programmer thinks they write clean code when they really really don't. Often I find the act of writing comments makes you go back to the code and clean things up, so it's still worth encouraging comments.

This is the way. In 'some' cases comments are perfectly fine. Like when you need to document 'why' something was done the way it was our to link to a specific piece of documentation.

When you start commenting 'what' the code does, you code is not self explanatory enough. And those comments will get outdated and need refactoring too. Just more unnecessary work.

I just get AI to write my comments lol. I'll paste the function or component and tell it to write comments in tsdocs format and it works great every time (I will also add to it sometimes of course).

Don't get me wrong, I also write clean code with good function and variable naming, but I find comments are also useful for a few reasons; they make the code even more quickly readable, they can explain why the code is the way that it is, and my favorite reason, they make it so when you hover over a reference to the commented item in an ide you get an explanation of exactly what the code does and what it expects without having to find and read the code itself

If you think a block of code needs a comment, turn it into a method and give it a proper name instead.

Really depends. Yes, if someone doesn't get what's wrong with this statement, they should. But you shouldn't wrap something in a method all the time just because. Sure, maybe you can make it an inline method, but usually, a method call takes time, and while it's not a lot of time, in constrained or complex system that can accumulate. A lot. Sure, the compiler might optimize stuff away, but don't just go blindly trusting your compiler.

Sure, a method call for something that gets called once a second is not a problem. But when you suddenly have thousands and thousands of method calls when say, you click a button, which calls method x which calls method x1 which calls y1 and y2 which call z1-10 and so on, then the method calls can suddenly turn into a problem.

Maybe not on a fast, modern device, but on an older or more constrained device. If your code never runs on there, sure, don't bother.

Could a pre-commit hook have caused the murder to not get committed?

Here is an alternative Piped link(s): https://piped.video/7LBLESXAJh0

Piped is a privacy-respecting open-source alternative frontend to YouTube.

I'm open-source, check me out at GitHub.

This is why I leave my phone in the basement when I get home.

I wish, companies just expect you to write garbage code as quick as possible, only to create tens of bugs afterwards that will take way more time than it would if they had left you enough time to do it correctly