Better question: - 200 lines of statically typed, pure functional code with high test coverage - 20 lines of code with I/O, parallelism, mutable state and/or

Better question: - 200 lines of statically typed, pure functional code with high test coverage - 20 lines of code with I/O, parallelism, mutable state and/or interacting with external APIs I find it way less cognitively draining to review a big chunk of blue ocean code with good patterns, than even small amounts of code which requires me to maintain any kind of state in my head, or try to think about the consequences of how this change interacts with the broader system. I'd say that some kinds of code are easily 10x more cognitively draining than others.