Just do TDD instead

If you’re writing an explanation of what your code does then, ding ding, you’re writing code. If your code has so many side effects and garbage in it that it’s incomprehensible without an explanation then it’s shit code and I doubt you’d be able to write a comment that explains it that is not equally as shit as the code. Commenting on how shit code works cannot be trusted because the commenter has already proved they’re shit at the job by creating that shit code.

Best you can hope for is the comment contains a reason as to why the code is shit.

The problem is that code is language and people who write shit code tend to write shit comments, so no value is gained anyway. The sort of person who’d write good comments will most likely write good code where these comments are not needed, and when they intentionally write shit code they’d probably explain why.

So best you can hope for is that both of these people write comments about why they decided to write a comment, and hopefully the person who writes shit code improves over time.

Idk, large chunk of my CS class was extroverted. They liked to party, many were in relationships and we often went for pints between lectures at the campus bar.

There ofc was a lot of weirdos and assholes around too, an above average amount, but they got outnumbered by normal dudes.

Had a decent amount of women but by the end of the 1st year like half of the class was gone and most women left. They found it boring, too technical or they were not really ready for university, same for the dudes that dropped out. There ofc was sexism, but that came from niceguys or dudebros, they exist in every field.

As for my professional life, most sexism I saw was from career managers and finance staff.

A classic

Yeah, you never see this in enterprise settings. Sure builders or streams can get a bit long but you just pop each .x() on a new line.

And when they're on new lines intellij has a cool feature where it creates a little UI only comment next to the line showing what type it returns.

Yeah that can get ugly but it’s still better than writing native queries because you know it’s gonna automatically translate to any db specific sql flavour.

When they get a bit too long and ugly I either write default methods using specifications or I create a more concisely named default method that wraps the verbose monster.

I find ChatGPT more coherent than stackoverflow in many cases. Sure it hallucinates and sometimes acts like it has dementia but at the very least it won’t write 5 paragraphs about how the framework behind my issue works without giving any examples.

Stackoverflow is good for finding alternative approaches, getting explanations for how stuff works in the framework, and error investigations. Useless for getting information on stuff you don’t already know.