I think you and the parent comment are onto something. I also feel like the parent since I find it relatively difficult to read code that someone else wrote. My brain easily gets biased into thinking that the cases that the code is covering are the only possible ones. On the flip side, if I were writing the code, I am more likely to determine the corner cases.
In other words, writing code helps me think, reading just biases me. This makes it extremely slow to review a LLM's code at which point I'd just write it myself.
Very good for throwaway code though, for example a PoC which won't really be going to production (hopefully xD).
Maybe it’s bc I’ve been programming since I was young or because I mainly learned by doing code-along books, but writing the code is where my thinking gets done.
I don’t usually plan, then write code. I write code, understand the problem space, then write better code.
I’ve known friends and coworkers who liked to plan out a change in psudocode or some notes before getting into coding.
Maybe these different approaches benefit from AI differently.
Very good for throwaway code though, for example a PoC which won't really be going to production (hopefully xD).