4 ms·
> motivated cs students who want to learn more than what their typical operating system courses has to offer. When I studied at UT, the OS course lets you buil
by eshvk 12y ago
> motivated cs students who want to learn more than what their typical operating system courses has to offer.
When I studied at UT, the OS course lets you build an OS. It was brutal. 80 hour per week brutal. But what I took away from the course is not the class notes but really the Prof/TA comments when we used to come up with design issues when we fucked up lower abstraction layers or subtle, really really subtle bugs that were introduced at previous levels.
To be honest, I am not sure how that would be replicable in book form if not accompanied by a teacher. Either you are so vague that people muddle, then google and your book is effectively useless. Or you are so prescriptive that people end up reading a floor plan to build an OS and get squat out of it.
- sosagain 12y ago>Either you are so vague that people muddle, then google and your book is effectively useless. Or you are so prescriptive that people end up reading a floor plan to build an OS and get squat out of it. Finding a middle ground is of course key.
- brudgers 12y agoI look at the books in my library. The middling one's are more or less reference materials. But the good ones -- On Lisp, JavaScript Allonge, HtDP, or SICP? None are dumbed down. The author is trying to impart all the knowledge that they can impart coherently. Knuth stands above them all of course. But its cautionary tale is that it's a book about compilers. I'm pretty sure I'll live to see chapter 12, but as it stands today, there are four more chapters to be released before it. Knuth began writing The Art of Computer Programming in 1962.