Something I find interesting about the large number of semicolon anecdotes in the comments is, as usual, LISPs got it right a long time ago. Unbalanced parens

Something I find interesting about the large number of semicolon anecdotes in the comments is, as usual, LISPs got it right a long time ago. Unbalanced parens look weird even to non-programmers, and not wrapping up something you know is a "packaged unit of thought" also looks intuitively wrong even to non programmers. But should this line end with a semicolon; or not; hard to say Also, REPL driven development vs 100 lines of text you don't completely understand and pray it compiles and good luck understanding the errors in a 100 line program, although a one line REPL usually isn't hard to figure out which line had the error (LOL). You need not wear out your paren keys forever, but it might not be all that awful of an idea to at least start with a LISP like Scheme or Clojure or whatever, just to get the basics down. This is, uh, not a new idea or an original idea of my own. Could do worse than pick up "Little Schemer" book. Someone should write the "Little Clojurist" book... assuming someone hasn't already. (edited to add, embarrassing, I searched the publisher of the Little... series for the obvious title and found nothing, turns out there's multiple crowd sourced projects along this general line, none official or commercial, or probably, legal)