> In code, comments are our signposts
No. Naming and good architecture are. Intuitive folder trees. Concise docs. Clear separation of concerns such that naming can suffice.
The more comments you need to ‘map’ your code, the worse of a job you’ve done.
jarofgreen•33m ago
Disagree. Personally that sounds like a massive barrier to reading the comment to me. Limited width column text is generally regarded as easier to read, make your comments easier to read. Especially as I probably have the code open in a limited width window, as that's what I expect from code.
dozerly•29m ago
verdverm•24m ago
Lindby•22m ago
Cockbrand•17m ago
This is a bit like vim vs Emacs - everyone should be able to use their favorite setup, and the formatting should not get in the way of the engineer's preferences.
ezrabuenk•15m ago
tacomagick•11m ago
jarofgreen•11m ago
Personally, I would have hoped by 2026 we had better IDE's and tools for managing code in text files such that developers with different preferences for a number of characters in a column or things like how you display comments can be accommodated. Yet still teams end up arguing about what standard to use.
someothherguyy•20m ago
https://en.wikipedia.org/wiki/Code_folding
jarofgreen•9m ago
someothherguyy•6m ago
there are also extensions for vscode that do this, vim plugins, etc