What Books Have I Written?
My philosophy in writing books has been strongly influenced by my college teaching experience in information technology and software engineering - clear descriptions of basic principles, philosophy and motivation for using a specific technology, and then clear examples of how to use it in practice. In a book with limited pages, it's not always possible to cover every topic, or to provide all information on a specific topic in the detail required to perform a particular task. I see the role of trade books as "breadth first, depth second" - these books provide orientation, but if you need intimate detail on a specific application, function or method, then you will almost certainly need to consult vendor documentation. For example, the Sun administration reference collection for Solaris contains many thousands of pages of detail, which can be daunting at first, but very useful in the long term.