I'd say your second bullet point encompasses a number of sub-skills, such as: * Understanding common coding patterns, and inferring design intent from them *

I'd say your second bullet point encompasses a number of sub-skills, such as: * Understanding common coding patterns, and inferring design intent from them * Quickly prioritizing "critical" vs. "nice-to-have" components of a desired feature (and reprioritizing as you learn more about the implementation constraints) * Being able to take a partially-complete or slightly buggy implementation, and quickly identify what's wrong with it (e.g. by interpreting compiler errors or using a debugger) * Gaining confidence in the correctness of code by spending a reasonable amount of time on testing, without going overboard