Hasn’t anybody told him what eating pussy means?
A software engineer that loves Disroot and the team behind it.
Hasn’t anybody told him what eating pussy means?
I definitely agree that too many comments is often a bad sign, esp. when large part of them is obviously generated.
As mentioned in my other comment, names will rarely explain the reasons why a given solution was chosen. These reasons are important from maintenance perspective and should be recorded next to the relevant code.
You’re definitely not the only one.
In my opinion the important information we should record in comments is WHY, because the code can only explain HOW, maybe WHEN, but never WHY. If we don’t know WHY, any refactoring done in the future could break the logic by ignoring assumptions made by the authors.
I often skip meetings without agenda. If they don’t care to prepare a reasonable invitation, I don’t care to join. Also - I skip meetings where they announce stuff. Announcements should go to my inbox, so I can read them when ready, not when they think it’s suitable for them.
Why marry a turd in the first place? 🤷