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.