Timothy Henry, coauthor of Data Abstractions & Problem Solving with C++: Walls and Mirrors, winner of a 2016 McGuffey Longevity Award: “I have expanded the writing and explanations in both the material I prepare to support lectures and the assignments I give to students. This provides an opportunity to practice a writing style similar to the one we use in our books and to receive feedback from students on the effectiveness of the writing.”
- Textbook & Academic Authors Association Blog article on “Getting Started and boosting your confidence”
Timothy Henry: “I ensure I have a good block of time with no meetings or classes. With my schedule, I have come to accept a block of 2 to 3 hours as valuable (though I do occasionally have an entire day). Because that is a short window to write, my normal writing day begins by clearing my desk and work list of distractions, such as minor ‘ToDo’ items, urgent emails, etc. Then, my email, phone and other messaging apps/devices are turned off so there will be no interruptions. I try to have any needed research completed outside of my writing time, since research can be done in ‘snippets’ of time.”
Carrano & Henry: “We are most proud of these key pedagogical features:
- Security Notes.
- Relatively short chapters that provide focus one a topic.
- Chapter dependencies and content are designed to give an instructor great flexibility in the order topics are covered. (Concept/Abstraction Chapters, Implementation Chapters, Language/C++ Chapters).
- Many diagrams that clearly show step-by-step how algorithms work.
- That the differences between steps are highlighted with color. (As opposed to a single diagram with numbered arrows to show sequence).
- That the book is culturally sensitive.”
Carrano & Henry: “We describe the features of the book, major changes in a revision, and remain receptive to user questions and suggestions. We are open to email correspondence with both instructors and students who use our book.”
Carrano & Henry: “After publication of an edition and even before the first book is sold, we maintain a list of tweaks or changes that we either could not make during production or that occurred to us after publication. During the course of the edition’s lifetime, we collect any comments and suggestions that are made to us by current instructors and students. About a year before the next edition will go into production, I ask the publisher to get reviews of the current edition. We analyze these reviews and decide how these comments and suggestions fit with our own ideas about how to improve the book. We also look at any updates or changes to the programming language discussed in the book to see whether the changes are relevant and need to be covered. Typically, we discuss the plan with our editor.”
- Textbook & Academic Authors Association Blog article on “Scheduling writing time and getting involved in marketing”
Timothy Henry: “I now clearly understand the phases/steps in the process. Ask for a clear timeline from the publisher.”
- Textbook & Academic Authors Association Blog article on “Advice and lessons for other writers”