Jason GormanWe spend roughly 10x as much time reading code as we do writing it. A tool or technique that makes you twice as "productive" at writing code *at best* makes you 5% more productive over all. Making your code easier to understand will have 10x the impact. But that doesn't sell tools or put developers out of work, so you won't be reading about it in Forbes.
Graham Lee, D.Phil@jasongorman there's some maths missing here. If I double my writing rate then I double the amount I have to read, so I become 90% worse overall not 5% better.
Haelwenn /элвэн/ 
@leeg @jasongorman Kind of logic and revelation which reminds me of the various explainations about why you should avoid writing clever code, for example:
>Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.
— Brian W. Kernighan and P. J. Plauger in The Elements of Programming Style.
>Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.
— Brian W. Kernighan and P. J. Plauger in The Elements of Programming Style.
@lanodan @jasongorman s/clever //