4 ms·
Productivity isn't about writing lots of code. For example: if you spend 48 hours writing 10,000 lines of code, and then I produce same functionality in a norm
by itamarst 9y ago
Productivity isn't about writing lots of code.
For example: if you spend 48 hours writing 10,000 lines of code, and then I produce same functionality in a normal 16 hours of work, with just 1,000 lines of code. Who is more productive?
So instead of focusing on writing lots of code, focus on solving problems. The less code it takes to solve a problem, the better off you are, because that's less code to maintain.
This attitude (explained in more detail here: https://codewithoutrules.com/2016/08/25/the-01x-programmer/ https://codewithoutrules.com/2016/08/25/the-01x-programmer/) then leads inevitably to the idea that working long hours isn't actually useful, nor is working at 2AM a good idea. The best way to be productive is to think, and that is easier when you are well rested, and works better if you take breaks and go do something else (https://codewithoutrules.com/2016/11/10/work-life-balance-software-engineer/ https://codewithoutrules.com/2016/11/10/work-life-balance-so...).
- jwdunne 9y agoI quite like the point of the article but I have one issue with it. It begins by focusing on "producing times ten" and then goes on to equate that with "lines of code times ten". The issue with that is lines of code isn't production. The real production is the value behind that code. If you do the same thing with a tenth of the code, you _are_ producing ten times more.
- fosco 9y agoboth of your comments reminded me of the 'the parable of two programmers' [0] (not original). While I disagree on the concept described that each programmer was 'productive' in writing 'lines of code' I think that the lesson learned is more about approach and how solutions should be evaluated. [0] http://www.bruceblinn.com/parable.html http://www.bruceblinn.com/parable.html