1. Empathy, as April Wensel talks about a lot (e.g. https://medium.com/compassionate-coding/confessions-of-a-recovering-jerk-programmer-b9d531a05ea9 https://med

1. Empathy, as April Wensel talks about a lot (e.g. https://medium.com/compassionate-coding/confessions-of-a-recovering-jerk-programmer-b9d531a05ea9 https://medium.com/compassionate-coding/confessions-of-a-rec...). You need this for everything from gathering requirements to debugging. 2. Ability to gather requirements: why are you building what you're building? (More here: https://codewithoutrules.com/2017/02/19/ai-replace-programmers/ https://codewithoutrules.com/2017/02/19/ai-replace-programme...) 3. Focus on solving problems, and when you're more advanced identifying problems. This means coding becomes a means to an end, rather than your goal. (more here: https://codewithoutrules.com/2017/07/10/stop-writing-software/ https://codewithoutrules.com/2017/07/10/stop-writing-softwar... and ) 4. A focus on productivity, which means a focus on doing less work, and specifically unnecessary work. This goes against the grain for many programmers, who want to code. Goal is to solve problems with as little work as possible, though. (More here: https://codewithoutrules.com/2017/10/04/technical-skills-productive/ https://codewithoutrules.com/2017/10/04/technical-skills-pro...)