5 ms·
People have different ideas of value. I see a method that sounds like that and a 429 and I have a pretty good idea of what is going on without someone taking up
by bobkazamakis 4y ago
People have different ideas of value. I see a method that sounds like that and a 429 and I have a pretty good idea of what is going on without someone taking up more lines to describe the method than execute it.
- brian_cunnie 4y ago> I see a method that sounds like that and a 429 and I have a pretty good idea of what is going on Yes, you're a seasoned HTTP developer. The comment isn't meant for someone like you. It's meant for the other developers on a shared codebase who may not know much beyond the standard HTTP status codes (200, 400, 403, 404, 503). > taking up more lines to describe the method than execute it It's a one-line comment. the Ruby code with the exponential backoff, eight lines. It does not take up more lines than the method.
- hbrn 4y agoYou split developers in to two categories, but how do you know those are correct categories? What if there's another type of engineer that only knows about 200 and 400? My approach is that conventional knowledge doesn't need to be documented in comments. Attempts at guessing how much conventional knowledge someone is lacking are futile. Those comments are similar to: int a = 4 // set a equal to four If someone doesn't know what 429 is, they should get confused, do their own research, and learn. Comments should not be turned into educational material about open standards, they should be about your business. There are much better places to learn about standards.