When code is a maze, smart developers make maps

(medium.com)

7 points | by boxesnlines 21 hours ago

2 comments

  • jarofgreen 16 minutes ago
    > Typically keep comments on a single line without line breaks — if a comment is useful, developers will scroll to read them, if it’s not they can easily scroll past it.

    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 13 minutes ago
      Who doesn’t have soft wrapping enabled in 2026? Line breaks are irrelevant
      • Lindby 5 minutes ago
        Soft like breaks in a code editor? That's insane
        • Cockbrand 0 minutes ago
          And so the war began.

          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.

      • verdverm 8 minutes ago
        Who makes assumptions about how others do things in 2026? Line breaks are apparently relevant, review agents complain about them, soft breaks are super annoying for vim motion users, opinions are still like ani
    • someothherguyy 4 minutes ago
      What? You don't like horizontally scrolling 6000 columns to read something?

      https://en.wikipedia.org/wiki/Code_folding