This T-SQL Tuesday post comes to you courtesy of Jason Brimhall (B | T | G+) regarding standing firm in something you did or some action you took in your career.
From his blog:
The idea for this theme is to start with a little self reflection. Then to come up with a story relating to one of these words: resolve, resolution, or resolute. Here are some examples of how these stories may be portrayed.
All of these words are very closely related. It is up to you to determine how you would like to apply them to your T-SQL world. Your experiences and stories can be loosely or tightly coupled to T-SQL, it is up to you.
- Resolve: A system outage occurred and you “resolved” it.
- Resolute: You made an executive decision and did not waver from it.
- Resolution: You discovered a bug and documented a work-a-round resolution for it.
- Resolution: You have discovered certain T-SQL skills are fuzzy and want to sharpen your ability in that area.
- Resolute: You are determined to improve performance in your application.
So, having set this up, I would like to tell how I Resolved to change my career form Jack-of-All-Trades in the IT realm to something more than just an Accidental DBA.
Having been in IT for 16 years, I found myself in a position of being able to handle just about anything that walked in the door. From DOS commands and scripting to big server hardware to networking, routing and switching all the way through to VoIP. I started in the UNIX world, and that having all but faded away, pushed Linux as far as was acceptable in our Enterprise and I still did not find any single technology that could hold my passion as well as UNIX could.
Then came SQL. Finally, a technology deep enough to give me a challenge. I still held on to all my other jobs because it paid the bills, but now things seemed different. When I was working on SQL, other things that came in and needed my attention now seemed to annoy me. I was starting to view them all as distractions. I was an accidental DBA, but somehow that was taking over my focus. My wake up call came 9 years into a stint with my employer (yes, I know, unheard of), when company layoffs and cutbacks started happening. I was not too worried as it would take them hiring about 3-4 heads just to cover my load, but still, I yearned for a more singular purpose. I talked with a few colleagues and they all told me to go for it. I made an Executive Decision: I stripped my resume of all items that were not SQL related. Yeah, it looked rather scary. I had not spent close to two decades building a skillset just to omit 90% of it for my next job. But it had to be done.
And the rest, as they say, is history. This past year has been a dream. All SQL, all the time. I am even doing some Data Architecting now, working with the Dev team writing some new in-house apps.
The moral of the story: Don't be afraid to chase your passions. Even if it seems like you are going against the grain to get there, sometimes that is exactly what it takes. Let nothing stand in your way - be Resolute.