Category: Editorial

  • Choosing a Career

    This was a short week in the US with the Thanksgiving holiday. This is a time when many people in the US have a long holiday weekend and often get together with family for some time away from work. It’s also a tradition for many people to “give thanks” to the blessings and people in their life. It’s a good time to reflect and appreciate the things that go well for you.

    That doesn’t mean that many, or even most, of us aren’t looking to grow our careers. For some of us, that may mean moving into a new field. Is that a good decision? Will we like the day to day work? Those are tough questions, and while you might be enamored with some technology as a hobby, when you do the work every day, things aren’t always the same. I’ve certainly seen this with friends and colleagues that have dramatically changed the lives into a completely new field. What is fun a few hours a week may not be as interesting when it’s a 40-50 hour a week grind.

    At SQLServerCentral, we often see posts where a community member asks if they should learn x or y. Should they move into a new career, or what’s it like working as a person that does z? Those are good questions, and I ran across a nice blog post from Dev Nambi on what it’s like being a data scientist. If you’re interested in data science, this is a nice list of notes about his job, but even if you were thinking about becoming an HA specialist, or Power BI report writer, or something else, the post talks about things that make impressions with his job. I’d like to hear more about how others would answer some of these questions about their own work. I need to do some of this myself.

    There are also a few very good items that I wanted to highlight. First, Dev notes that you don’t learn everything in school and there is more to work than is learned in school. That being said, there are core concepts to understand. I think this is true in most fields. We need some good base knowledge, but there is more than that knowledge. We need to learn how to put concepts and requirements together, as well as continue to ask good probing questions about the task.

    The other item that is pointed out a few ways is teamwork. Communication skills, including body language and humor, are important. We are social creatures and while I think having a variety of skills, views, and ideas is important, we need to get along with each other. We need teamwork within an organization, but for our careers, we also need a team of people to help us. That’s our network. Those skills are important for all of us, no matter what the job.

    If you want to move into a new role and grow your career, you have options. You can use schooling, you can try to grow in your role, or you can learn things on your own and apply for new positions. They all work, but they all have some drawbacks as well. They also all require effort and motivation, so if you want to make a change, set some learning goals, and start working. Making strides in a direction will help you grow and get you closer to your goals.

    Steve Jones

  • Republish: A T-SQL Code Testing Guide

    The day after  Thanksgiving, and a holiday. So you get to read A T-SQL Code Testing Guide.

    Please do, I’m a fan of testing.

  • Thanksgiving 2018

    Today is Thanksgiving in the US, a holiday that most people get away from work.

    A reminder for all of you, no matter where you are. Be thankful for something in your life. We’re only here for a short time and we need to appreciate and find joy where we can.

    Enjoy the day and see you tomorrow.

  • Another Reason to Care About Security

    This is likely a short and quiet day for many of you with Thanksgiving in the US tomorrow. Most people have tomorrow off in the US, and those that do business with the US may have a quiet couple of days with little communication from the US. A good time to catch up on things.

    Before you go, I want you to think a bit about security today, and perhaps across the weekend before you come back. Security is important, and many of us that work in the data world know this. We see more and more data breaches occurring every week, with the rate of incidents at this point being a little over 4 per day. These are losses of data from all sizes and kinds of companies from household names to local law firms and retails organizations.

    Most of us work for some company that has data, and we know a portion of this deserves protection to ensure we don’t need to pay for identity insurance or get fined by the government. There’s another reason to care about security: branding. There’s a survey that just came out, which notes that consumers are likely to stop using a brand if there’s a data breach. There’s a report on the survey as well, if you don’t want to give up more data to get the data.

    Consumers note that many would stop working with a brand if there were a data breach, but that might not mean not using that service, just not using their online services. This makes some sense in some industries, but not others. I also know that consumers can be emotional and look to leave a service, like a mobile phone provider, after a breach, to move to a new provider. In many cases, this may create churn as most providers have had some breach, and it’s entirely possible whoever is last is the one losing customers this quarter.

    What I did find interesting is that more consumers are being careful what information they share, preferring to use official portals rather than email, even avoiding clicking on links. To me, this is only a matter of time before customers stop providing most voluntary information, or the start to make up data values. That might be a problem for those of us that look to analyze data for our employers. If quality falls, perhaps we’re less valuable.

    We need to do a better job of securing system, patching them against vulnerabilities, writing better software, and preventing exposure of data. We’ve gotten better in recent years, but we need to do more work, including avoiding keeping extra copies of sensitive data in development and test environments. It requires work to mask or remove this data, but it’s better than the risk of accidental exposure and brand damage.

    Steve Jones

    The Voice of the DBA Podcast

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