(skimming intro & conc) reads like a joke paper: - their top characteristic is "writing good code" - they censored the specific VCS - they describe their ins

(skimming intro & conc) reads like a joke paper: - their top characteristic is "writing good code" - they censored the specific VCS - they describe their insights as (inter alia) "ecologically valid" ---- This is HN, so... I'd approach the title as "when is x10 possible?" - insight of a far simpler or faster etc implementation (e.g. better choice of modularity, factoring out hidden commonality, dynamic programming); - insight about a better way to achieve the end result - might be no code at all So I'm talking about insight. What personal qualities lead to insight? (note that there isn't always a better way to be found, so personal qualities don't guarantee it) - be really really smart. Especially, large working memory, to be able to see connections. Or at least be able to load in (cram) the information temporarily. - the ability to step back and notice the bigger picture. Executive function. - ability to manage stress, so they have the breathing space to do that (the wisest engineers will choose a workplace that makes this easier) Skill in proofs is a predictor: flexibility, handling complexity, managing the top-level purpose as well as the detail (forest-for-trees), noticing connections. Mathematical knowledge itself can help sometimes too. But probably the skill in any intellectual discipline is an equally good predicator e.g. philosophy, history, law