"Best practice" is a horrible term. Best for what mix of goals and situation? Is it REALLY the best EVAR and every single alternative has been checked and evalu

"Best practice" is a horrible term. Best for what mix of goals and situation? Is it REALLY the best EVAR and every single alternative has been checked and evaluated? It's weasel words, intended to give more credence to the advice that it has proven. As for these recommendations, these aren't bad or good, even worse, these are mediocre. Want my advice? Have your logging statements double as comments. Logging and comments both should concentrate around difficult code. So why double them up? Javadoc was the last "good" idea in comments I ever saw: generate documentation from comments. Unfortunately it didn't provide enough autogeneration abilities or semantics to track evolving code. Nor do comments and javadocs integrate git history or help indicate heavily modified and evolved code, something I think could also be done. I believe Rust enables some use of markdown in comments as well, that is a good idea. IDEs, even intellij-level, don't really help out with comments and doc-comments much either.