A framework for learning hard technologies: learn, experiment, build, teach. The speaker built three prototypes in a weekend not to ship them, but to study and build a library of technical skills that later support products, consulting, or new ideas.
Build to study. I have a learning framework I call learn, experiment, build, teach, which is how I ingest information. And this weekend was about building. And I built 3 different significant technically challenging products. And none of them are probably going to ship into the market because that's not the purpose of them. The purpose was to learn about these relatively hard technologies that they were associated with. And as I start building out that intellectual property of how I, you know, can work with these much harder things that can eventually turn into, you know, something else, or into a consulting practice, or in some other kind of product, what have you. So when I— when people are asking like, hey, when you're building, does that count as shipping? Does that count as studying? Does that count as selling? I tend to think the vast majority of building should be considered studying, because the vast majority of building is about getting information into your head. If you're doing those kinds of experiments, if your purpose is to be learning more, then when you have an understanding of like what's in the market, where the market needs are, you have this library of technical supply you can apply to create extraordinary value.
