Text Book Writing

About 10 years ago now I was sitting in the teacher’s lounge and the mail came in. There was a package for me and it was tossed on the table in front of me. Seeing the return address I knew exactly what it was and hurried to open it. One of my friends asked what I was so excited about. I explained that it was my new book. Misunderstanding she replied something about everyone getting new books to review all of the time and that it was nothing to be excited about.

I slid the book over and asked my friend to look at the title page. That is when she realized that when I said “my book” I meant a book that I had written. That first book was just a book of projects and nothing like the complexity of a textbook. But it was published work and I was pretty excited about it. Since that day I have updated or re-written that project book twice (the C# version was a re-write the VB .NET version really an update), written a complete VB 6.0 textbook and re-wrote someone else’s VB 6 textbook to work with Visual Basic .NET. I recently collaborated with others to create a third edition of that book for VB 2005.

Today I got a letter from my publisher saying that the newest edition of this Visual Basic 2005 textbook has just been released. My author copies should be following soon. I still find this pretty exciting. Of course the most exciting thing over the years has been hearing from teachers who actually use books I have written in their classrooms.

I always found picking out textbooks to be a chore. Is the reading level right? Are the right things covered in the right order? Are the projects reasonable? How is the sample code? There is an endless set of questions. Sometimes I used to think it would be easier to just write my own textbook.

Honestly the first textbook I wrote was pretty much the course I taught at the time. The order was the order I used in class. The examples and projects were the projects I used in class (though I had to add some of each to fill out the book) and of course it worked out just fine for the way I taught. Ironically I never got to teach from that book because I had to assign the VB course to someone else the next year.

Writing a textbook is a lot of work but it is rewarding. Not in money really because authors have to sell a lot of books to make any real money. Authors who write for a living have to write full-time and turn out several books a year to make a living. But it is rewarding in personal satisfaction.

Comments (4)

  1. Are you talking about FUNdamentals of Visual Basic?  

    I personally LOVE that book and think it is more than "just a book of projects".

  2. AlfredTh says:

    No that is not what I was calling just a project book. VB FUNdamentals was my first real textbook. That’s the book I based around my VB course. I’m glad you like it. Frankly I really regret that I wasn’t able to convince the publisher to do a second edition for VB .NET.

  3. Mr.Higgins says:

    Already requested a Desk Copy from the publisher…should be here tomorrow.

  4. Best of luck with your new book. You understand students and high school teachers so I’m sure you’ll be successful with the book.

    Maybe more high school teachers will work with vb.net as the first language they should teach students with it.

Skip to main content