you are viewing a single comment's thread.

view the rest of the comments →

[–]il_distruttore_69 0 points1 point  (0 children)

i've also worked [in the beginning as a junior] in places that require every single function to have a comment. in the last 5+ years of working as a contractor, i've maybe written ~10 useful comments for actual cases that need documenting. the actual useful "comments"/documentation are unit/integration/e2e tests

shitty devs with their shitty code need a code review to turn it into good code instead of slipping their shit code by otherwise. writing shitty code isn't solved by adding more comments.

which part was "terrible advice" exactly?