Voice of the DBA

Tag: career

  • R-E-S-P-E-C-T

    Working for one company for your whole life. Spending your career with a small company that engages and lives in the local community. Seeing your management and co-workers around town and at leisure events. Being a part of, and loyal to, a company doing business around the globe.

    This sounds ideal to me, as I prefer working for smaller companies, and I want to work for a company that respects my time. In fact, I do work for a company like that. Red Gate, is in many ways, like the German Mittelstand described in this article on work life balance in. We work hard, we do need to respond to issues outside of “normal hours”, but for the most part employees treat others in the company (and our customers) with respect. That’s the key to managing an around-the-clock, global business that you are proud of.

    It’s unlikely that most companies will change their view on how employees should be treated, and what amount of work is expected. Certainly many companies in the US have had lots of success by driving employees to work harder and longer, especially requiring this of their technology staff. Many of us that do work with computers have been well compensated, but the time lost and stress induced are high prices to be paid and many employees struggle with these requirements. There is numerous evidence that long work hours don’t result in more productivity over time, but when companies want to move forward, or systems are broken, companies expect that staff will work.

    I don’t think laws like the German Anti-Stress law that limits contact after work hours can help things. The culture of work really needs to evolve to find a balance between getting work done and respecting employees. I’m not sure I’ll see that change at any scale, but I do know there are more companies, especially smaller ones, that do want to retain and invest in their employees, respecting their time and efforts. They don’t guarantee lifetime employment, but I do think they make life better while you work for them.

    Steve Jones

    The Voice of the DBA Podcast

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

  • A Little Empathy

    In the past, there have been times as a DBA when I’ve been annoyed by the clients submitting tickets to IT. I’m not sure if those incidents were more frustrating than the work I’ve done as a developer for customers, but both can be very annoying and stressful for an employee. I’ve probably acted poorly and said things I didn’t mean while I was upset. I hope I’ve learned to do better by now.

    Things were worse earlier in my career, mostly because over time I developed a more perspective and empathy, both of which Tim Mitchell talks about in his post on perspective. I learned that no one was intentionally trying to be difficult. Each customer or client had their own tasks, and often it was technology that was slowing them down. The only reason they asked me to do some work was that they couldn’t get their work done.

    Much like Tim, I learned that technology doesn’t exist for technology’s sake. If you just want cool technology handling a task, buy a Raspberry PI or Arduino, get some sensors, and build something amazing. However, if you want to be successful in Information Technology, and have people value your applications, systems, and services, learn that you need to solve problems. Learn how to make other people’s work easier.

    I’ve had plenty of success in my career by following Tim’s advice. I’ve made myself part of the business and learned how I can address the problems and challenges faced by others after I’ve learned what those issues are. I’ve also learned that just asking a business person to tell me what to do often results in neither of us being successful.

    Steve Jones

    The Voice of the DBA Podcast

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

  • 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.