> When I "program", 95% of what I do is read documentation and other technical resources That's very off from my work. For me, it's the opposite: 95% is writin

> When I "program", 95% of what I do is read documentation and other technical resources That's very off from my work. For me, it's the opposite: 95% is writing code, navigating code, testing code or doing stuff in the shell. Reading documentation usually makes only a small amount. And even then, writing notes makes a good part of it too. > conceptualize what I want to happen, and construct the corresponding logic flow, while trying to anticipate potential problems and corner cases. I can also do that while typing. Mindgears are no reason to stop typing.