Makes a lot of sense to me, most of it. I think they idea that you can't learn important software engineering/designing lessons from a book is overstated thoug

Makes a lot of sense to me, most of it. I think they idea that you can't learn important software engineering/designing lessons from a book is overstated though. But it is true that most of the existing books probably don't include some of the types of case studies and lessons that you would get from a job. But I think that textbooks should simulate those things with exercises. Of course a textbook can't include real dynamics or interactions but it's not true that it's impossible for some of those lessons to be in a book or at least touched on. I mean, a textbook could actually emphasize things like digging in and iterating to really understand the problem in depth. The criticality and difficulty of understanding the problem and finding the right framing for the problem, realizing that is something that should be deliberately shaped to enable the solution. To me the most challenging thing has always been the power imbalance between myself and the managers or users who are incorrectly framing the problems, and the struggle to negotiate an adequate problem definition that will enable a good outcome.