“Aside from mediocre marks in his freshman literature courses — even MIT wanted people to be literate, but evidently Peter Zimmer didn’t care for poetry — the kid was straight A.” (bold type added for emphasis)— Excerpt from The Sum of All Fears by Tom Clancy
At the Friday night speaker’s dinner, Eugene Meidinger asked me what I thought was a very good and valid question. I’m paraphrasing what he said, but he asked me something like this.
“I’ve been reading some of your ‘blog articles.” (Ed. note: hey, someone reads my ‘blog!) “Most of your articles don’t have anything to do with SQL. Do you ever write anything about SQL? How did you get involved with SQL Saturday? Are you one of those people who just happened to latch on to SQL or hang out with SQL people?”
The answer is not simple. This article is my attempt to answer his questions.
To answer his first question, yes, I have written about SQL, but it’s been a while. For his (or anyone else’s) reference, here are some of the SQL articles that I wrote.
- SQL Server: How to get started
- Installing SQL Server 2016
- Installing a Baseball Database
- Setting up a primary key
Yes, I do have experience in SQL Server. However, I am not a SQL MVP, nor do I consider myself a SQL expert. As I describe myself, “I fall under the category of knowing enough SQL to be dangerous.” (Or, as I like to think of it, I know enough SQL to be able to do the job.) Although I don’t know enough to be able to talk about advanced SQL techniques, I can discuss beginner-level SQL topics that can help people just getting started in SQL. I’ve been meaning to write and present more beginner SQL-related topics, but (primarily) lack of time has kept me from getting them done.
(I’m also at a bit of a disadvantage because I currently work in an Oracle, not a SQL Server, environment.)
I won’t rehash how I got involved with SQL Saturday (I’ve already done that; I’ll leave it to you to check the link and read it for yourself). I’ll just simply say that, although I don’t talk extensively about SQL topics, I’ve learned that there is still a place for me within an endeavor such as SQL Saturday.
When I first started my ‘blog, I intended for it to supplement my SQL Saturday presentations. Since then, however, it seems to have taken on a life of its own. It’s become a forum for me to express my thoughts in a way that they’d be helpful for both myself and for other people, especially anyone pursuing professional careers.
One thing that has come out of these efforts is that, professionally, I’m finding myself more and more. I’ve had to come to terms with my own level of technological knowledge and expertise. For years, I’ve been seeking positions in programming and application development. But a funny thing happened along the way. I discovered that while I do enjoy coding, I wasn’t passionate about it. I wasn’t willing to spend late nights and downtime doing more with it or to immerse myself in it. As soon as I came to that realization, that was when I realized that I should look into something else.
And as soon as I came to that realization, good things started happening for me. I became happier and more confident in my career direction. I started getting more and better opportunities.
It also made me realize that, despite all my jokes about being an odd man out because I was “not a SQL expert,” there is still a place for me in SQL Saturday. No, I may not be presenting SQL or data topics, but I am still making important presentation contributions to the database and IT communities.
Back when I worked at Blue Cross in the late 90s and early 2000s, I fulfilled a role in which I supplied server staff with information they needed to do their jobs. As I describe it, my job was to “support the support staff.” It’s only within the last few years that I really appreciate just how important of a role that was.
Ironically, although Eugene asked me the original question, it was one of his own presentations that made me come to this realization. The increasing difficulty of keeping pace with technological trends contributed to my waning passion about some technological topics. I mentioned a while back in a podcast that I thought it was important to play to your strengths. By focusing on something about which you’re really passionate — in my case, it’s technical communication — there’s no telling how far you can go.
So Eugene, if you happen to be reading this, hopefully this answers your questions and gives you a perspective of where I’m coming from. (Good to see you this past weekend, by the way!) And for anyone else reading this, hopefully this will inspire you to reflect upon your own interests and skill sets, and provide you with a sense of guidance as you pursue your career interests.