Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Well, this is a stupid rant.
BambuSource15783130dFrontend mostly is readable.
I'm curious about your assembler w/o comments
OP has obviously not worked with other devs before.
Root33706130dYou could not be further from reality if you tried.
numb3rs706130dI'm not saying that comments are bad I'm just saying make them useful, for Buisness stuff put it in a wiki page. Nobody wants to see comments like this :
//Getting object from database
Root33706130d@numb3rs This rant is a trainwreck. Your third word was "stop." There are no instances of "useful," "better," "improve," etc. in your rant; it literally tells other developers to stop commenting their code altogether. This is a bad thing. Furthermore, a wiki is absolutely not the place to document code -- any such comments are substantially less likely to get updated there, meaning this practice strongly encourages divergence between documentation and function due to the added workload required to maintain it.
So no, this is terrible advice and it should be followed by no one.
Please refer back to your third word.
RemyRm5351130d@Linux thanks for the tag.
@root basically said it all.
@numb3rs there's a HUGE difference between readable code and good code. any code can be made readable, but it's not always the most performant.
Besides that not everyone has the time to dilly-dally on reading every fucking line in a function tens or hundreds of lines long.
A simple, well put comment can describe it way easier saving alot of time for any devs that have to work on the project after you. Even if your code is readable.
So get off your high horse and start adding comments.
Sincerely every other that's going to read your code after.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job