Voice of the DBA

Tag: career2

  • Staying Successful

    This is an interesting piece on data predictions. There’s a college that’s using data to help students, but not in the way you might think. Rather than customizing learning plans or finding more efficient ways to teach, the college is analyzing data to find students that might be struggling with college life overall and intervening early to help them cope with college and continue to move forward in their studies before they drop out.

    This is similar to something HP has done, trying to predict if employees might leave and intervene to see if something can be done. I heard an interview with the HP managers, who praised the program, and found they were among the most likely candidates to leave the company. However HP also realized that identifying people likely to leave allowed their HR people to try and find creative ways to retain their employees.

    I’m not entirely sure this is a process I’d like to be a part of, but it does seem like HP is doing well in their experiment. They realize they can’t solve every issue and keep every employee, but they can work proactively to try and reduce the losses. However privacy is a big part of this data analysis and I hope HP keeps that in mind as they move forward.

    Steve Jones

    The Voice of the DBA Podcast

    Listen to the MP3 Audio ( 1.8MB) podcast or subscribe to the feed at iTunes and LibSyn.

  • My 2015 Plan

    I started this on Jan 1, but with family commitments, I ended up delaying it until today. I wrote about having a 2015 plan, and thought I should build one as well. I’ve tried a few things in the last couple years, and while I haven’t stuck to the plans, I have thought that my years were successful. This year I’m hoping to do a slightly more formal plan.

    I’ve broken this down into a few areas, all of which should help my career. These are the high level areas, and while I have some plans, I suspect that life will get in the way and things at work with change, so I have to be flexible.

    Certification

    While I’m not sure certification really helps me in my career, I do know that it is something that catches eyes on resumes. What it means after that is up to you and how you sell/market/position it.

    However I do know that certification efforts can drive learning. I took a number of the SQL Server 2012 exams when the product was released, but never took the last one I needed for certification. I didn’t have the time to schedule it at the time, and it’s bothered me every since. I need the 70-462 exam for the MCSA certification.

    In November or December, I noticed Colleen Morrow writing a series on exam prep for the 70-463 exam. It got me thinking. I should follow along, study, and then take the exam. Since I have a relatively light travel schedule for Q1, this is something I want to work on.

    PowerShell

    I tried to do the Powershell Challenge last year with the book Powershell in a Month of Lunches last year. I used to take the book, my laptop, and work through exercises while at my daughter’s volleyball practice. I reached a point where I got off track, had some networking issues, and ended up not completing it.

    However I learned things. I ended up writing quite a bit about Powershell and using it to accomplish small tasks. In the new year, I want to use it more, and one of the places it to replicate lab setup for new machines and rebuilds. That’s the goal as I build out new systems in 2015.

    I do want to complete the challenge, but we’ll see how it fits into my schedule.

    Speaking/Travel

    Last year I actually spoke less than 2013, but it felt worse. I think the problem was too many events in too short a period of time. Three in a few months and four in one. I need to balance that out in 2015.

    Red Gate is also looking to change some of our SQL in the City seminars. We may end up doing more private, as well as all day, training seminars on our tools and the Database Lifecycle Management (DLM) topics. I expect that I’ll need to spend more time here, which means less other events.

    I’ll likely also skip some of the bigger conferences. I’m speaking at SQL Konferenz in Germany and (hopefully) SQL Bits. I will likely submit to DevConnections, but that may be it. The multi-day events are a time sink and drain and if I’m going away for a few days, I think I’d rather invest in myself at a SQLskills event.

    As far as SQL Saturdays go, I think Q1 is the first time I don’t have a speaking engagement in a quarter. The Jan ones came up too fast for speaking deadlines at the end of the year and I wasn’t sure I was up for a trip. With overseas trips in Feb and Mar, I’m not sure I’ll make any, though Pordeone in Italy is tempting.

    I am thinking to get to Madison and New York City, but this might be a year where I speak at less than 10 of them. That’s usually been my goal, but scheduling is getting harder. Certainly Puerto Rico is tempting, as is Ottowa. We’ll see how many pop up and where in Q2/3/4 and I’ll work out a schedule.

    I also expect to evolve a couple of my talks and change them around. I’ve usually added a couple talks each year, but this year might be tough. If I get one more done, I think that will be plenty.

    Writing

    Writing has been mostly editorials and small content for the last few years. I’ve written a few articles over the break, and I’m looking to do a few more across the next few months as I delve into new topic areas. It’s a time sink, but I want to be sure that I get some longer technical writing done.

    Lab

    The last thing I need to do is build a better lab. I started setting one up last year and it worked OK, but I had a drive die with a few of the VMs on it (I know, I need backups. See PosH above), and I got busy. It also wasn’t quite the right design, and I was unclear on a few of the AO/AG/FCI items. We’ve had a lot of content this year in those areas, partially with me pushing for it, and after my day at Allan Hirt’s pre-con, I want to rebuild it in a new, better way.

    I also want to make it a better, more replicable setup. We’ll see. This may help with the speaking above, and certainly the other items, so I want to get going on this, preferably thinking about building up a small, portable device with labs.

    Conclusion

    I’m writing this post so that I can go back and evaluate it again at the end of the year. I’ll compare how I did and see where the plan failed, and where it changed. Without a doubt, things will change.

    I do have a reminder every month to go back and look at goals, so I’ll be checking this post each month to see how I’m doing it.

  • The 2015 Plan

    This is the last day of 2014, and we begin a new calendar year in 2015. It’s a time that many people make resolutions and I’ve got a few you might think about for 2015.

    The first one is that I’d urge you to be sure you find some balance in your life in 2015. Whether you’ve had balance or not, remember that life is short, and you never know when you will leave. I’ve had friends die early, and I was touched by recently reading this last post from Derek Miller. We can look forward, we can plan, but we never know what the future will bring and what life will drop in our path.

    If I look back at my life, there are many things I’ve chosen to do, or lived through, that I might not have imagined even five years before the experience. It’s unlikely that I’ll be able to guess with any accuracy what will happen in the next five. No matter what your beliefs, I do think that you must continue to live you life while you are on Earth, and hopefully the best parts of that life are outside of your career.

    That being said, while you find a balance with life outside of work, don’t neglect your career. For many of us, our careers have grown over time as we learn more and gain skills. Make time in 2015 to do this somehow. I’ve got two suggestions for you to work on building skills, no matter what your job.

    The first is to pursue a certification. I’ve been interested in Collen Morrow’s series on prepping for Exam 70-463. We can argue about whether the certification proves anything, but I do know something it does do. It guides your knowledge growth and gives you a goal. Both are good things that can help you improve your skills. It’s also motivating to learn new skills and pass a test. Colleen has inspired me a bit as this is the last exam I need for certification and I may follow along with her and take the test in 2015.

    The second thing I might suggest is tackle a project of your own. It could be a piece of software, a database design, a web site, anything at all. Build something, write about it, display it to the world. Whether it’s practical or not, whether it’s useful to others, it will showcase your skills in whatever areas you tackle. This also gives you a goal to work towards, as well as a potential resume item that can help you in your next job search.

    It’s amazing to think that 2015 starts tomorrow. I hope you all have a happy, safe, and enjoyable celebration tonight.

    Steve Jones

     

    The Voice of the DBA Podcast

    Listen to the MP3 Audio ( 3.1MB) podcast or subscribe to the feed at iTunes and LibSyn. 

  • Moving On

    I’m not leaving; I have the best job in the world, and I could easily see this being my last job. However, we’ve had a few people leave Red Gate recently, a few of which I have known for some time. It’s inevitable as a company grows that there will always be some people that find better opportunities or need a change of jobs. Perhaps it’s a sign of the times, but I doubt that many of us in technology will keep the same job for decades.

    Leaving a job isn’t a bad thing, and it certainly doesn’t have to be antagonistic. I’ve left quite a few jobs on good terms, with both myself and my employer wishing each other well in new endeavors. I have found most people will behave as adults and professionals, even when one side is not happy with the way in which the employment relationship ended. Being open and honest certainly helps, as people usually respect a position if they understand it, even if they don’t like the circumstances.

    One of the things that typically happens at Red Gate is that the person leaving sends a note around to the department(s) affected, and sometimes the company. Recently we had an interesting one come out that was broken into different sections. Each section looked back at this person’s time at Red Gate, and the note got me thinking. How would I look back at my time in various companies?

    The sections talked about good times, things learned, mistakes made, memorable events and more. It’s the type of perspective I like, and what I’d like to write if I ever leave. Then I thought maybe it’s the type of thing I should write every year, looking back at the good and bad times I’ve had at the company.

    Taking stock of your situation, the good, bad, challenging, growing, and other events, is a healthy way to examine your employment. I might encourage each of you to write a “leaving letter” as we close out the year. Write down the things you’ve had fun doing, the achievements you’re proud of, the mistakes you’ve made and more. Don’t limit it to 2014, but look at your entire time with this employer. Use the letter to evaluate your position and career. Maybe you’ll think about how you’d like next year to proceed, or even if you want to change companies. Either way, stepping back and reviewing your career is something that is valuable to ensuring you continue to move in a direction you want.

    Steve Jones

    The Voice of the DBA Podcast

    Listen to the MP3 Audio ( 2.7MB) podcast or subscribe to the feed at iTunes and LibSyn.