3 ms·

For a mature programmer like you, it probably feels redundant to write a book that iterates concepts you have understood long ago. This book is for beginners. I

• brudgers 12y ago
  Though mature, I'm well within the criteria you describe. Perhaps that's why I am a little familiar with what is already available for beginners. The issue for undergrads isn't that resources don't exist, it's that they don't know what exists. Twenty years ago my CS major neighbor turned me on to Mosaic, but had never heard of Dr. Dobbs. And he was a senior. A year ago, I was talking with a CS Junior who knew nothing about what an embedded system was. He only became aware at a job fair. Hadnt heard of YC either, sohe got my copy of Hackers and Painters. Anyway, the danger you face is that you've cut the scope all the way back to undergraduates and begun to cast it as a traditional textbook. One that has to introduce C and x86 assembly and has to address the practical issues of testing and running a new minimal OS on their development machine [under Windows, OSX, and Linux?]. How much of what you want to write gets left out and how much of what you do write winds up being superficial instead of what you wish you had known?