> A common advice for documentation is "why not how", I'm not sure you can do "why" by looking at the "how".
You are right. It’s the rule when you write the doc.
But when you are let alone in an unknown codebase, having your IDE summarize the "what" in the auto completion popup could be really useful. Especially in codebases with wrong naming conventions.
You are right. It’s the rule when you write the doc.
But when you are let alone in an unknown codebase, having your IDE summarize the "what" in the auto completion popup could be really useful. Especially in codebases with wrong naming conventions.