Engineering Notebooks

I was instructed to keep notebooks by my engineering professors when I was getting my degree in Electrical Engineering. I was told that all good engineers kept notebooks and so I dutifully obliged. When I went to work for Oracle Corporation right out of college, I continued to keep notebooks and have kept every single one. My professors told me that my employers would want to retain my notebooks when I left but not a single company has ever asked for them.

Naturally I started a new notebook when I joined my current company and have filled two volumes. My coworkers see my notebooks and have been known to make copies of various pages. I have even had several people mention that I should write a book. I tell them I have and that it was a lot of work for very little pay. Lately I have been thinking about writing another book though. The only problem is that people don't really read technical books any more. It is much easier find information on the Internet. Then my boss suggested I write a technical blog, string the entries together, and create an electronic book of sorts. I suppose I could do that with this blog, but it is far too diverse for a single book. Besides I try to keep my entries short and simple so that everyone can understand them.

The book I want to write is very technical and so this evening I will be starting a second blog. Don't worry, I will still contribute to this one so that I get my 71 entries per year. My second blog will be a deep dive into PostgreSQL. PostgreSQL has some of the best documentation for any computer software, whether commercial or open source. However it lacks a cohesive set of examples and certain solutions to real-world problems. My hope is that my new blog will work hand-in-hand with the existing documentation and add clarity to some rather difficult concepts. Hopefully it solves a hole that I feel exists currently.