Voice of the DBA

Tag: career

  • Micro Credentials

    For all of my career, there has been a constant debate about the value of certifications. Early on I saw one boss move ahead because of his CNE (Certified Netware Engineer) credential. That got me moving in that direction, though I switched to an MCSE (Microsoft Certified Systems Engineer) track once Windows gained prominence and I found myself working in that arena.

    These days there seem to be less certifications around in one sense. Certainly Microsoft and other vendors are spending less effort building and maintaining a program. At the same time, there is a variety of different products that you can get certified in using online learning. A friend recently showed me the Redis University where you can complete courses and get a certificate. We even have Redgate University, designed to help you improve your ability to use our products.

    Like many credentials, completing a course doesn’t mean you are an expert, or competent, or even qualified with a product. There are numerous stories of people holding credentials and being unable to perform simple tasks in the real world. I’d counter with the fact that there are plenty of people with lots of experience on paper that equally cannot perform fairly rudimentary tasks. I do think that people that have made an effort to complete some course have likely learned something.

    Microsoft Philanthropies is experimenting with micro credentials, an idea of helping people to learn skills and tasks that aren’t equivalent to formal education, but perhaps can take the place of other educational opportunities, such as a college degree. It’s an interesting idea, and it fits nicely with my thoughts that your career requires continual learning and improvement, or as they put it, up-skilling.

    There is a great quote in the article:  “Careers are no longer ladders. They are more like vines in a rainforest. You can swing on one and then grab another.” I think that’s true in technology, and likely true in many other fields as well. I’ve seen plenty of issues with workers trying to undertake year+ long programs to retrain in some other field, only to find out there aren’t enough jobs or the skills are becoming obsolete quickly.

    The future, in my mind, is that we need to be adaptable and flexible. We should have some basic skills, like logical problem solving and communication, but the specific syntax and muscle memory to work on any particular implementation are something we need to pick up quickly and gain competence in without a long learning period. This doesn’t mean that expertise isn’t valued, but flexibility and the willingness to continue to improve skills over time is more valuable.

    Will this replace traditional universities in our business? I don’t know, but I do think it could. There are still places where a formal education is valuable and useful, but I’m not sure if it matters in the field of technology. At the same time, unless organizations that hire individuals stop requiring four year degrees, I’m not sure this matters. I hope they do, because a degree says something about you, but not necessarily more than other experiences and efforts that you can undertake.

    Steve Jones

    Listen to the podcast at Libsyn, Stitcher or iTunes.

  • Learning from Exercise

    A long time ago I decided to run every day. I did for a bit, in fact, I had a neat milestone along the way and continued on for 1564 days. That was quite a memorable period in my life, and one that I look back upon fondly. I’ve aged a bit, and while I could do it again, I also have decided there are other things that matter more to me, so I have moved on in life.  I learned a lot from that time, lessons about myself and life that continue to help me today. Some of them even apply to work and my career, little nuggets of wisdom that help me find ways to find success in my life.

    Apart from some better fitness, one of the main benefits for me was the sense of accomplishment. I had no bad days where I would think I wished I had run. None. That seems obvious, but it also provided me some comfort that I had moved things forward in my life. I took that lesson back to work, where I sometimes have bad days. I have days where nothing goes right, or I have people that take over my day and schedule.

    I know there are also a number of things that I need to do at work, which aren’t that important, or even aren’t that critical, but they provide a measure of satisfaction that I’ve moved things forward. These days that is often getting things scheduled for the newsletter. In the past it might be doing a little space extrapolation (though I’d just look at this in SQL Monitor today). Low value items, but I get some accomplishment in the midst of otherwise stressful times when I get something small done that is on my list.

    The other thing that came from the running streak was the feeling of getting away from other parts of my life. Whether with family or work, I might be overwhelmed or stressed or otherwise out of sorts in my day. Taking 20-30 minutes for myself was a way of resetting my day, and it was a welcome break. While exercise is my thing, and even today it’s a priority around work, I’ve had other crutches that help me cope. I love to read, so taking 5 minutes to escape in a book every day is something that feels similar to exercise.

    I know other friends that might play a short game, play with a pet. Having some other consistent, distracting activity is a good release when things are tough. No matter how busy we are, or what’s broken, taking 5, 10, 15 minutes away can help refresh you and get you ready to go back into the trenches and deal with others.

    I’m sure jobs exist that can’t spare the time, but I’ve never had one. I haven’t always realized it until later, but I wish someone had told me to take 10 minutes away in a crisis to reset myself and then come back. I know I’ll remember that the next time I end up being stressed during an IT problem at work.

    Steve Jones

    Listen to the podcast at Libsyn, Stitcher or iTunes.

  • Good Resume Examples

    I talk about resumes, enhancing your career, and finding your dream job at various events. This might be one of my most popular talks, and I’ve been lucky enough to give it to many audience across the years. Quite a few people have taken my advice and used it to further your careers, and I’m always pleased when I hear from them.

    I don’t give any great advice, but I do try to get people to think about how they present themselves. Your resume (or CV) is often the first way that you present yourself to a potential hiring person. Even if you’ve used your network and someone gives a recommendation for you, your resume is the first way the interviewer sees you.

    In the Brent Ozar newsletter a few weeks back, he had a link to a “how to write a resume” guide. There are a lot of tips, but I agree with Brent that the layout in a number of these samples is really nice. At least, it’s well spread out and easy to read from an organizational standpoint.

    A couple things I’d disagree on. First, be careful of colors. Personally, in the “reverse chronological resume format” example, the blue is hard for me to see, even on my 26” monitor. Be careful about colors that don’t provide enough contrast. Plenty of people hiring are my age.

    The other thing I disagree about is the skills being too prominent at the top. Remember, I won’t spent a lot of time looking at the resume, so be careful of drawing too much attention away from your summary or work experience. I usually search for skills, so take advantage of the 30s of my attention and impress me with a well written opening.

  • Contracting for Work

    Throughout my career, I’ve primarily been a full time employee for an organization. I have worked for myself, as well as for consulting companies. For the latter, I’ve been an employee as well as a contract worker. There’s a bit of difference between those, at least in the US, and it isn’t always easy to understand what that means for an individual.

    I thought about my various experiences while reading about Jon Shaulis’ T-SQL Tuesday post recently on changing his mind about contracting. He also has a section on T-SQL (bonus points for Jon), but the post is mostly about contracting and employment. Jon talks about some of the differences he’s seen between working for someone as a contractor and as an employee. His experiences are similar to mine, but I certainly wish I’d had a good list of these things when considering job offers in my 20s.

    There are lots of people in our #sqlfamily that have started consulting businesses, wanting to work for themselves and make more money. You can read various accounts of how well this works, but it certainly isn’t as smooth for everyone as it might seem. I like reading Brent Ozar’s yearly evaluations, and I’ve been following Eugene Meidinger’s journey as well. These aren’t about contracting too much, but they do give you an idea of what it’s  like to operate your own business, and as a contractor, you are your own business, though you have a little less of the “business” stuff to do since someone does the admin, selling, and marketing and just tells you what to do.

    I actually encourage everyone to consider themselves and contractor and don’t get too complacent with your job as an employee. You never know when you situation will change, and it’s good to be prepared. It might not even be you, as your spouse or partner might force you to make a change.

    Or your employer might.

    Just like a contractor might have one client for 10 years, I think it’s prudent to keep an eye on the environment and be prepared to find another client if some unforeseen event occurs. The days of single company employment for life are over for most of us. I have the best job, but I keep an eye on the market. One never knows when things might change for them.

    Deciding how to structure your employment is a decision each of us should make, but do so with an open mind and some understanding of the changes for work, benefits, savings, medical coverage, and more. While Jon has a good list, I’d love to see more people build and publish a structured checklist in terms of decisions and costs, even sample ones. This can help others get an idea of what the impact might be on their life when making a decision like this.

    No matter whether you choose to work for an organization or as a contractor, it’s not a final decision. You can change your mind anytime, though do so with some planning and consideration of the impact on you and your family. It’s not an easy decision, but you should be comfortable with your choice when you finally do make it.

    Steve Jones

    Listen to the podcast at Libsyn, Stitcher or iTunes.