Interesting article, as I feel the exact opposite. The more time I have to parse out what code does and fix bugs along with that, the less time I actually get to code. The lack of syntax highlighting is an exercise in frustration for me, it takes me 10x longer to read and therefore understand. So too with Copilot, I can now write side projects twice as fast, if not faster. That, to me, is where the real fun occurs.<p>I do understand where the author is coming from though as I have friends who have similar setups, monochrome editors with no LSP. Talking to them, I believe they are ADHD or neurotic adjacent, where if the red squiggle is not dealt with immediately, they stress about or have anxiety over it, so the author must be similar. I think they can't relate to others because most others simply don't care. Hell, I'm the same way as the author about phone notifications, as I turn most off and those I don't turn off, I feel like I must deal with immediately as well lest I be anxiously thinking about them, and yet I see so many that have dozens of notifications active. But I simply don't feel the same way about code and writing, while the author does.<p>Anecdotally, I've been having a blast with ChatGPT Plus with GPT 4. I can ask it interesting programming questions and it provides novel insights. The other day I was thinking of how one could make a better GraphQL type interface, and ChatGPT suggested that the query language also handle local state, ie, there is no local or server side state, it's all just <i>state.</i> I was curious about that and asked it more, going down the rabbit hole as to how the syntax and semantics would look. Best of all, I could do it all on my phone through their app, while I was walking or doing other things. It felt like having another senior engineer who would endlessly trade ideas with you, never tiring.