Well, he has a point. If you need a variable to be colored to know it's a variable, then I'd argue that you don't really know what you're doing.
If you don't need a variable to be colored to know it's a variable, then why do you color them?
A counter argument would be that you have this huge visual cortex in your brain which can use cues like this to help you quickly find what you're looking for.
A counter argument to that would be that you should know your code well enough to not need to rely on anything like that.
When I started programming, I had notepad and that was it. I didn't need colors. I use colors now, though. What's that say? I have no idea.
Not everything you do is about need. I think highlighting helps reduce some of the cognitive load involved in mentally parsing a code block. Especially in a language you might be unfamiliar with. I also happen to like the way it looks.
> A counter argument to that would be that you should know your code well enough to not need to rely on anything like that.
that's not a counter argument to that. nobody in the world no matter how brilliant knows giant complicated codebases inside out. and the best way to parse those is to use colors to aid your brain in differentiation. otherwise its all one garbled mess.
If you don't need a variable to be colored to know it's a variable, then why do you color them?
A counter argument would be that you have this huge visual cortex in your brain which can use cues like this to help you quickly find what you're looking for.
A counter argument to that would be that you should know your code well enough to not need to rely on anything like that.
When I started programming, I had notepad and that was it. I didn't need colors. I use colors now, though. What's that say? I have no idea.