I suspect there are a number of factors that eliminate people from these steps like objectivity, persistence, and other virtues.
The biggest single discriminator that the Y Combinator people talk about, which I agree with, is doing the right things first without regard for scale. Most developers will immediately jump to some framework so that they can prop up some web app in the shortest time and immediately go into promotions and then struggle with scale when they need to scale.
I had this big app that tried to solve for full decentralization of universal file system access from a browser. I wrote my own end-to-end test automation tool and focused all my energy on software execution performance. These things allowed me to prove out new ideas and identify regression in about 8 seconds on a single machine or about 2 minutes on 5 machines talking to each other. Most people won't invest in that. I could perform a massive refactor across dozens for files and hundreds of lines without regression in about 2 hours. At work, at that job at that time, I spending more than 2 weeks for tiny refactors that were littered with regressions and having to clean up other people's messes.
Worse, is that most people recognize when they are not performing well, especially if it is anywhere from 10-100x less well. The normal go to place is either sympathy or an echo chamber. High performers don't do that. They aren't trying to impress people with their awesomeness or seeking sympathy when it falls apart. They just build what they need at great expense because its something they can have that others won't have.
The biggest single discriminator that the Y Combinator people talk about, which I agree with, is doing the right things first without regard for scale. Most developers will immediately jump to some framework so that they can prop up some web app in the shortest time and immediately go into promotions and then struggle with scale when they need to scale.
I had this big app that tried to solve for full decentralization of universal file system access from a browser. I wrote my own end-to-end test automation tool and focused all my energy on software execution performance. These things allowed me to prove out new ideas and identify regression in about 8 seconds on a single machine or about 2 minutes on 5 machines talking to each other. Most people won't invest in that. I could perform a massive refactor across dozens for files and hundreds of lines without regression in about 2 hours. At work, at that job at that time, I spending more than 2 weeks for tiny refactors that were littered with regressions and having to clean up other people's messes.
Worse, is that most people recognize when they are not performing well, especially if it is anywhere from 10-100x less well. The normal go to place is either sympathy or an echo chamber. High performers don't do that. They aren't trying to impress people with their awesomeness or seeking sympathy when it falls apart. They just build what they need at great expense because its something they can have that others won't have.