>> "Domain expertise" might be the main thing he's talking about This is clearly what he is talking about. When he is talking about his experience with the "Se

>> "Domain expertise" might be the main thing he's talking about This is clearly what he is talking about. When he is talking about his experience with the "Senior Design project course in Computer Science at my alma mater" he is really talking about how people can "MVP their way into getting domain expertise" at some level. This is a fundamental problem with the "startup industry". Groups of people from a computing (I want to be broader than CS) that have reasonably strong technical skills and a lot of enthusiasm for applying those skills want to build successful startups. They generally lack domain expertise outside of technology-adjacent products for the most part. It's not completely absent because there is some success, but there isn't a balance for the most part. Where does the domain expertise come from then? It could come from a slow development process involving the founders immersing themselves in the area. That's really only something that's going to be feasible before the founders create the company. Once the company has been founded, it becomes a scramble to interpret some ideas and build an MVP that can be sold to some of the advisors that the founders could get time with. It's only now that the foundational work is happening. If the right people see the MVP, or the founders make the right connections, it's possible to catapult forward from here, but it's a predictable failure point.