Earlier quoted context omitted.
It's definitely situation dependent. When writing a lot of frontend code (vue, typescript, css, tailwind, html) I know what I'm typing several mental steps before I actually type it, so speed gains there are most pronounced. Sitting somewhere in the middle are dynamic languages where there might be certain implementations (say... some random api integration) where it's simply a lot of code I've typed thousands of tim…
> I never understood the argument "I spend more time thinking than coding". You are still going to write the same amount of code whether you're thinking or not. My ideal world (why I love typing fast) is that that time of me coding gets brought down by 50-200% over someone who types slow. My perspective on this (I'm not a fast typist, but don't feel it's a big limitation) is that I can think while typing, so if I can…
The reason for that is that a codebase will condition the complexity and thus time it takes to add features to it, in a way that is similar to algorithmic complexity and big o notation, except we as human can't even afford polynomial complexity and constant factors matter a lot.
Imagine you're developing an API, both server and client. You can cut your time in half by automatically deriving the client code from the server side specs. Of course you may have to develop that tool yourself and it takes time. The point is that the time invested developing it will be repaid each time you implement a new endpoint in your API, cutting development time in half:
n * (t(s) + t(c)) versus n * (t(s))