I think this is up to interpretation. Optimizing for output could mean "improving the system", polishing your soft skills, rather than spending that 20% learnin

I think this is up to interpretation. Optimizing for output could mean "improving the system", polishing your soft skills, rather than spending that 20% learning how to code in assembly. On the other hand maybe that assembly knowledge would have lead to creating something that would make others more productive, and end up saving years of combined humanity productivity. It is entirely up to the human in question on how time is utilized. Unfortunately, most of us are just happy with our performance. We are having "meh" performance and then we look at others that achieve things and we think its luck and good timing.. While there are cases of luck/good timing, in most cases people spit blood, coding/hustling endless hours, pushing themselves constantly, being modest about their knowledge, being methodic and efficient. And the best part is that they are like pigs in mud, they enjoy it to the max. Even if everything failed, they would still emerge with a sense of achievement, just like kids playing with legos. This is what the take away from this article should be, choose your path and execute like a boss. You are not a snowflake that can do things in 1 hour vs. 1 week, you are a spoilt kid thinking you are awesome, ending up wasting your true potential.