I love to write. It is how I express myself best. During the last fall I was pondering starting on a book, my first one. I’ve heard many people talk of the experience. Some enjoy it, others think it is too much work in return for too little. (We don’t need a lot of intelligence to figure out that writing books does not yield a lot of money). I wanted the experience, not the money. I was also a little afraid of over committing to a solo-writing project – mostly because of the many other commitments I had. I wanted something relatively light that would get me started as an author, and if it was something I enjoyed doing – I could take up more projects going forward. Last fall was also a time when I was going through some serious decisions with my career – I was not sure I wanted to remain a pager-carrying operational DBA for longer than I already have. I knew many people in the community – so I could talk through my needs with them and figure out what to do next – but, what if I didn’t? What if I was one of those many people who really didn’t have a ton of contacts or friends and was unsure of where to take his/her career next? We all need to read stories of others to form our own – noone is entirely on a solo journey. We need to know what is out there, how to make ourselves seen/heard and find out what worked or did not work for others like us. And most importantly, we are at a juncture where then are a flood of new technologies, hundreds of different ways of doing the same thing – we need to know what to learn that is likely to be the best for us. It occurred to me that I would personally benefit from a book that talked to a lot of successful people in the data profession and made me understand how they dealt with their career and how they got to where they were. There are a lot of podcast interviews available..so why a book though? This occurred to me too – I am a huge fan of podcasts and listen to as many as I possibly can during my daily walks. But here was what I found – it is hard to find specifically who you want to listen to and when. You have to be ok with subscribing to what the podcast channel puts out there, and many times the questions are not about any career direction, they are an in depth discussion of the technologies the person has been working on. I did not want this to be a technology discussion – there will absolutely be some of that as most people here are gurus at what they do, but it had to be more around providing people direction.
This is partly what got me attracted to the ‘at work‘ series of books that Apress has – I thought an addition to this with the data profession as focus would be useful to many people.
After my proposal was accepted – I had to do the hard work of finding the people to interview for this. My publisher and me agreed that we wanted a blend of data folks – DBAs, BI/Analytics people, Product Managers, Technical Editors and such. I wanted people who did not have books to their credit, as it would be a joint launch pad for me as well as them – but we decided that we’d need a few known names there too, just to make the book attractive to people who read often. So most of people chosen here are those who have not written books before, but a few aren’t. This worked fine. A few other things did not work as I thought they would- as below.
1 My initial decision to go for a cross cultural blend of people did not work out well. The process for this book involved interviewing the person, transcribing the interview using a third party transcriber service and then editing it for the book. I discovered the hard way that american transcriber services did not do foreign accents well at all. They even had trouble with various american accents such as strong southern ones. So I had to restrict myself to local people to interview and work with.
2 As the book matured I found it easier to work with a blend of verbal interviewing and letting some people write their answers down. This again was not something I knew at the start of the book and was a learning experience. By the time I got here I had very little time left – so interviewing people across time zones or countries became very difficult to do. I am explaining this in a lot of detail because I sincerely did try to get a diverse group of people on board and that became very difficult to pull off.
3 A third lesson was this – this was a fairly time consuming project. It did not take a *lot* of time, but it did take time and commitment from people involved. Some people committed but did not have time for the follow up and for making the corrections/changes needed. I had to replace them with other people and move on.
4 The last lesson was also this – some people just did not have much to say although they seemed very skilled at what they did. It could be that their experience was limited, it could also be that they are not used to talking much about what they do at all. Talking about myself is still a difficult thing for me. I could understand that. But a book needs content to fill a few pages – so my understanding of that was not sufficient to push it forward. I had to leave those people out too.
I want to apologize in advance for any hurt caused to any of these people – it was not intentional and absolutely nothing personal.
That said, below is the star-studded list of people who are featured in this book. My long time dear friend/mentor/guide Kevin Kline has written the foreword.
I am insanely honored to have my name out there with them. I hope what they say will help you – it helped me in getting to where I am, and still does. The book will be out in October 2018, and will be available at the PASS Summit as well. I must mention special thanks to Jonathan Gennick of Apress for supporting and encouraging me, and to Kathi Kellenberger, who did the introductions and has been a friend/mentor to many in the community.
(Footnote: I tremendously enjoyed the experience and am already planning on another book).
Edited: The book is now listed on Amazon.com here. Am working on changing the category from Oracle(?!?) and adding list of interviewee names. Watch this space for updates.