increase software productivity

software deliberate practice

programming deliberate practice

programming self improvement

scientific approach to increasing software productivity http://blog.ninlabs.com/2012/02/memory-2-0-attentive-memory/

measure developer impediments (remove friction) instead of developer productivity http://dev9.com/article/2015/1/the-myth-of-developer-productivity

book on personal self improvement journey. somewhat generic content. https://hkelkar.com/2015/12/31/being-craftsman-the-book/

business approach to increasing software productivity http://www.leanessays.com/2003/11/software-development-productivity.html

time/task management http://www.stevepavlina.com/blog/2007/05/33-rules-to-boost-your-productivity/

generic but relevant https://blog.binarymist.net/2013/03/02/how-to-increase-software-developer-productivity/

generic but could be good marketing https://www.quora.com/What-are-the-best-ways-to-increase-productivity-as-a-web-developer-programmer

ericsson latest work - book peak https://www.youtube.com/watch?v=uoUHlZP094Q

research https://scholar.google.ca/scholar?q=deliberate+practice+&btnG=&hl=en&as_sdt=0%2C5&as_vis=1 https://scholar.google.ca/scholar?q=deliberate+practice+software&btnG=&hl=en&as_sdt=0%2C5&as_vis=1

deliberate practice strategies https://www.redgreencode.com/deliberate-practice-for-software-developers/

The Cambridge Handbook of Expertise and Expert Performance https://books.google.ca/books?id=voWlHWw980UC&printsec=frontcover&dq=The+Cambridge+Handbook+of+Expertise+and+Expert+Performance&hl=en&sa=X&redir_esc=y#v=onepage&q=The%20Cambridge%20Handbook%20of%20Expertise%20and%20Expert%20Performance&f=false

deliberate practice tips http://expertenough.com/2327/deliberate-practice-steps

developer level up (find how it was promoted) https://gist.github.com/jasonrudolph/1133830#file_programming_achievements.md

book https://en.wikipedia.org/wiki/The_Pragmatic_Programmer

famous 10 years http://norvig.com/21-days.html

multiple learning methods through practice https://en.wikipedia.org/wiki/Practice_(learning_method)

10x programmer http://www.construx.com/10x_Software_Development/Origins_of_10X_%E2%80%93_How_Valid_is_the_Underlying_Research_/

questioning deliberate practice vs natural talent https://www.redgreencode.com/making-sense-of-the-deliberate-practice-debate/

list of deliberate practices methods for programming https://www.todaysoftmag.com/article/507/how-a-software-craftsman-learns-deliberate-practice

good tips https://simpleprogrammer.com/2015/10/09/deliberate-practice-for-programmers-a-framework-for-learning-on-the-job/

http://dev9.com/article/2015/1/the-myth-of-developer-productivity So what do we do? Code is the output, but it’s not really what we do. If we were just transcribing something into code, that’s basically data entry. We’re knowledge workers. We take inexact problems and create exact solutions. Imagine if managers were capable of exactly specifying the system they want built. They would have to explain it so finely-grained that it would be programming. That’s what we do. We are people who exactly detail how a system works. Our code is the be-all, end-all specification for what the software does. We are people that write specifications, digest knowledge, and solve problems. Most people are incapable of breaking a problem down to the level required for computer code to solve it. This isn’t to say that they can’t learn, but it’s a skill you must nurture. Imagine a parent (P) trying to teach a kid (K) how to make a grilled cheese sandwich: Ask a doctor what their job is. Is it talking to people? Is it writing prescriptions? Maybe it’s taking inexact problems from imperfect people with imperfect information, then trying to diagnose and fix or ameliorate problems, within the constraints of cost, time, side effects, and a million other things. Sound familiar?