My mission to (almost) eliminate code comments
I have mixed feelings about this. I think it depends on the project you are working on. If your codebase can be packed into a few hundred lines of code, with nothing fancy or complicated and no code is being injected from elsewhere, then the author is absolutely right. Documenting what a function or a method does should be sufficient and imo you should do that in all cases, just for the sake of making it easier for new developers to jump into the project if they prefer using some fancy IDE. However if your codebase is composed of several million lines of code(like a lot of the ones I work on), things change. Using readable names is a perfect general advice but eventually you end up with complex logic, which is not necessarily the result of some developer who just wanted to get a task out of their way but could be as well a result of &quot;business needs this by Monday, 3 weeks ago&quot; or simply some mind boggling edge case which needs to be handled. In which case, adding some inline comment with an explanation as to why something is there and ideally a link to your ticketing system can be a life savior. I&#x27;m far not a fan of things like:<p>&#x2F;&#x2F; Increment counter by 1.<p>counter++;<p>You should never do that unless you are studying programming and you have been required to explain every line of code along the way(though I don&#x27;t know why a professor would ever want that, certainly no one ever asked me to do stuff like that).