Jeremy discusses the unique challenges of software design, emphasizing that building often reveals more than theoretical modeling. He contrasts software development with traditional engineering practices, highlighting the ever-changing nature of tools and libraries. Additionally, he reflects on the rationale behind the waterfall methodology, where organizations aimed to optimize resource allocation by sharing specialized skill sets across multiple projects.
