|
|
|
|
|
by washadjeffmad
954 days ago
|
|
I had a 1930s edition of a "radio physics" textbook as a child, and because there could be no prior assumptions about exposure or familiarity, it was filled with very complex ideas explained so cohesively and coherently that, well, I could understand. The author knew that this book was for people who might be as involved in the business of radio as its science or engineering, so they wrote as much about the application across every industry, breaking down the systems to the component level and manufacturers, deployment, and ordering, as they did the design and theory. I learned how to evaluate a textbook from its structure and style. It certainly wasn't designed for discrete lessons, and the professor would have needed a diverse and practical understanding to teach it effectively. |
|
I wonder if the same thing isn't happening with computer science. When I started studying the topic in the late 80's, I was part of the earliest generation that actually did, and everything seemed to be explicitly written with the goal of making sense. Some things (like recursion and pointers) were fundamentally complicated, but they were made as simple as they reasonably could be.
My son is studying computer science in college right now and I look at the way they present the material and it often seems designed to confuse - I'll read it over and then explain it to him the way _I_ was taught it and he'll say, "oh my gosh, why don't they explain it that way?"