2 ms·
The problem arises when you are focused on something very specific, for example designing a particularly complicated series of function calls, you effectively h
by stcredzero 16y ago
The problem arises when you are focused on something very specific, for example designing a particularly complicated series of function calls, you effectively have to keep a stack in your mind, think about locals, instance variables, whatever, abstract stuff that the brain isn't so well designed at retaining, which becomes very vulnerable to disruption.
Let me ask this: after you've written such code, how is it for other people to read it? What is it like for people to debug it?
I think a lot of the problem comes down to us using the brain for stuff it's not great at.
I think good programming design tries to maximize the stuff your brain is good at and minimize the use of stuff your brain isn't good at.
- rdtsc 16y agoNote he said "designing" not coding. When you design things, a lot of relationships and entities are in your head. If you are just fixing some unit tests or looking to do small cleanups or tweaks then yes, you can do that while chatting with your friend about the weather, and at the same time banging away at code in front of you. Your context is just 100 or so lines of code.