> Less interested in people and character studies.
If you don’t want examples then all you need to know is velocity. The Y Combinator people call it doing things that don’t scale. Here is how it works for absolutely anything:
1. Get the right tools in place. This is an intrinsic capability set you have to build. People tend to fail here most frequently and hope some framework or copy/paste of a library will just do it for them. Don’t be some worthless pretender. Know your shit from experience so you can execute with confidence.
2. Build a solid foundation. This will require a lot of trial and error plus several rounds of refactoring because you need some idea of the edge cases and where you the pain points are. You will know it when you have it because it’s highly durable and requires less of everything compared to the alternatives. A solid foundation isn’t a thing you sell. It’s your baseline for doing everything else at low cost.
3. Create tests. These should be in writing but they don’t have to be. You need a list of known successes and failures ready to apply at everything new. There are a lot of whiners that are quick to cry about how something can’t be done. Fuck those guys and instead try it to know exactly what more it takes to get done.
4. Finally, measure things. It is absolutely astonishing that most people cannot do this at all. It looks amazing when you see it done well and this is ultimately what separates the adults from the children. This is where velocity comes from because you will know exactly how much faster you are compared to where you were. If you aren’t intimately aware of your performance in numbers from a variety of perspectives you aren’t more special than anyone else.
People who accomplish hard things are capable of doing those because they didn’t get stuck. They had the proper tools in place to manipulate their environment, redefine execution (foundation), objectively determine what works without guessing, and then know how much to tweak it moving forward.
Thank you so much for putting these heuristics into words. My only question here is that a lot of what you wrote seems like best practice from the perspective of a person within the tech industry. Outsiders might call it common sense. So if everyone knows what they 'should' be doing, then why do so few actually follow through?
One answer to that question might be character. Angela Ducksworth has a book called, "Grit". It is a lot like character study, which the OG explicitly expressed their disinterest for. My intuition is no matter how well you can describe the steps for success, success is not replicable. If true, that would explain why there are hundreds of self books, thousands of coaches, and only a handful of people who can consistently excel.
Having said that, I hesitate to say that there are only a few people in the world who are exceptional due to a constraint I would describe as "genuine article". How depressing a thought that would be.
Carpe diem! Floor the gas pedal, and see how fast you can go. Maybe you'll break all expectations and fly into space.
Luck is a massive, massive factor. There are plenty of exceptionally smart and gritty people who fail, and plenty of far less-so who succeed.
Your argument is good if you just follow it to the obvious (if inconvenient) conclusion. Despite so many people “having the answers,” no one can replicate it reliably. And even the ones who can likely wouldn’t be able to if you removed capital from the equation. The clear explanation is: luck.
But of course luck tends to strike when you’re working hard and consistently, so it’s not totally out of one’s hands.
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.
If you don’t want examples then all you need to know is velocity. The Y Combinator people call it doing things that don’t scale. Here is how it works for absolutely anything:
1. Get the right tools in place. This is an intrinsic capability set you have to build. People tend to fail here most frequently and hope some framework or copy/paste of a library will just do it for them. Don’t be some worthless pretender. Know your shit from experience so you can execute with confidence.
2. Build a solid foundation. This will require a lot of trial and error plus several rounds of refactoring because you need some idea of the edge cases and where you the pain points are. You will know it when you have it because it’s highly durable and requires less of everything compared to the alternatives. A solid foundation isn’t a thing you sell. It’s your baseline for doing everything else at low cost.
3. Create tests. These should be in writing but they don’t have to be. You need a list of known successes and failures ready to apply at everything new. There are a lot of whiners that are quick to cry about how something can’t be done. Fuck those guys and instead try it to know exactly what more it takes to get done.
4. Finally, measure things. It is absolutely astonishing that most people cannot do this at all. It looks amazing when you see it done well and this is ultimately what separates the adults from the children. This is where velocity comes from because you will know exactly how much faster you are compared to where you were. If you aren’t intimately aware of your performance in numbers from a variety of perspectives you aren’t more special than anyone else.
People who accomplish hard things are capable of doing those because they didn’t get stuck. They had the proper tools in place to manipulate their environment, redefine execution (foundation), objectively determine what works without guessing, and then know how much to tweak it moving forward.