707
you are viewing a single comment's thread
view the rest of the comments
[-] platypode@sh.itjust.works 10 points 1 year ago

In my experience refactoring lots and lots of crappy code left by devs long gone, a dev who can write useful comments is by and large a dev who can write code clean and simple enough not to need them. If the code doesn't have informative names and clear separation of concern, chances are a comment won't help because the dev didn't really know what they did that worked in the first place.

[-] MagicShel@programming.dev 14 points 1 year ago

Generally, yes. However I have been known to document exactly why I'm doing something incredibly stupid - because it's required but a stupid third party library which, despite being awful, is still better than implementing it myself as a refactor.

[-] bappity@lemmy.world 3 points 1 year ago

a dev who can write useful comments is by and large a dev who can write code clean and simple enough not to need them.

my boss is great in this regard and also always has to keep reminding us to write unit tests ๐Ÿ˜…

this post was submitted on 24 Oct 2023
707 points (97.7% liked)

Programmer Humor

19623 readers
1 users here now

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

founded 1 year ago
MODERATORS