Comment by wombat-man

20 hours ago

I had a professor who asked us to print source code for our projects for him to read. Looks like he's still at it. I'm sure he's being driven insane in these AI times.

Wild, did he ask you to use a colored printer for syntax highlighting?

  • I program almost daily with only bold, italics and grey (for comments) in my vim rules for highlighting.

    I can read my code just fine.

  • we only had a black and white printer, I don't think they would spring for color. Also, iirc he had a script he had us run to print it, so it' not like we were printing straight from the editor.

    • RIP vim `:hardcopy` :( .

      For some harder C code (implementing `malloc` for example) my preferred debugging method was printing out the code and debugging it with a pen between classes.

      I eventually realized being inside an editor gave me too much attraction to thrash with "just one more quick iteration & debug run..." and could actually end up more time consuming than being forced to reconcile my mental model with what I had already written by me double checking my assumptions.

      Interestingly, some of my peers started picking up the habit for their own projects and we ended up having small "debugging" sessions by trading print-outs .

      1 reply →

  • Why would you need color to read and understand code?

    • Source code has a structure, and some parts are more important to the reader than others. Good syntax highlighting makes the important parts easier to see; bad highlighting gives all parts the same emphasis. Notionally you could use font weight to convey this in a black and white medium, but color makes this easier.

    • Yes. People complain about AI but the downfall of human cognition began when syntax highlighting, formatting and indentation were introduced. /s