I disagree that comments are an indication of messy code. The purpose of comments are to 1) translate low level concepts into higher ones for improved readability and 2) to maintain information in the design process that can’t be represented by the code itself.

Obviously I don’t have to comment mathematical operations, but it makes sense to comment the algebra of how I derived an equation and it’s use in the code. Now, I could refactor that section of code into a function in order to give it a name, but that would make it more difficult to read as the programmer would then have to find the definition of that function somewhere else in the file. It is objectively more spaghetti-like to pull out single-use code into a function rather than just label the block of code with a comment.

I’m guessing old CRTs. I’ve heard they can emit radiation if they aren’t lead lined.

I’ve been working on developing a CPU architecture based around my own variant of lisp called “dollhouse lisp” the big twist is that DHlisp executes code by reducing a syntax tree, so all code is destroyed once it’s been executed. It’s a very elegant solution, but a very difficult implementation. (Especially when it comes to loops and garbage collection.)

I would’ve expected Nevermore to be a kenku, but unless you really plan out your sentences kenku don’t have any unique mechanics, but aarakocra do. It’s kind of a shame, to be honest. I’ve been playing a kenku recently, and I’m not planning out my sentences or anything, but I do have an unconscious tendency to mimic people’s style of speaking, so I at least have that going for me.