Voice of the DBA

Category: Editorial

  • Don’t Be a Ghost

    Ghosts can be fun, but not when you're looking for a job.
    Ghosts can be fun, but not when you’re looking for a job.

    I talk about branding at many different events, with the idea that you should control your personal career brand, and make an effort to improve it. As more and more employers look to validate your experience and verify your skills, having a strong brand helps you to stand out amongst the competition. The cost of a bad hire is high, and companies are trying different things all the time to reduce the chance they’ll make a bad hire.

    I’m not the only one that thinks you should have some brand out there. Troy Hunt wrote a piece about being a ghost programmer and how it hurts your career. It basically talks about how a programmer that doesn’t leave any kind of trail on the Internet is not likely one you want to hire. There are all sorts of reasons someone might not have a blog, or participate on a site like Ask SQLServerCentral, but many of the reasons are signs that a person isn’t really working efficiently. I’m not sure I completely agree with this interpretation, but I do think that the less information a potential employer can find about you, the more reason they might have to ignore your resume and move on to someone who they can perform more due diligence on.

    I completely understand the desire for many people to keep their lives private. There’s nothing wrong with that, though it can be detrimental to your job search. However you can overcome some of this, but maintaining some documentation about your projects, skills, thoughts, and providing that along with your resume, or as additional proof to your resume when requested. You can even use anonymous handles on the Internet, providing them in the same manner you have “references upon request” on your resume. They can be sent in an instant, but they aren’t public. I’d even make a note on my resume to that effect, if I were inclined to maintain more privacy about my career.

    You don’t have to be a Jon Skeet or an Iris Classon, but you should have some information you can share about your career when you are looking for a job. If you don’t, you might never know how much it impacts your job search. After all, is your phone not ringing because you aren’t qualified or employers just don’t know if you are?

    Steve Jones

    The Voice of the DBA Podcasts

    We publish three versions of the podcast each day for you to enjoy.

  • Modeling the Earth

    The idea of modeling the Earth is an incredible challenge.
    The idea of modeling the Earth is an incredible challenge.

    Whether you agree with the science of climate change or not, the ability to work on a project like this one from Microsoft Research would be cool. The issue of carbon pollution and the potential impact on our world is huge. If we accept that global climate predictions of problems are true, we may severely impact world economies with the changes that some people have suggested. If we discount the problems and they turn out to be true, we may end up in an even worse position. It’s also entirely possible that climate changes are natural cycles of the planet and we have no need, or possibility, to alter the way the world is evolving.

    No matter what your position, it seems the Microsoft Research isn’t trying to make a stand for either position, but rather attempting to clear the technical hurdles that would allow other groups to compare and debate about their models with regards to any global issue. Their goal isn’t to push users in a direction, but give governments or other organizations tools they can use to either consider future actions, or react to new data or information that can be added to a model. There’s a short interview from CNN with one of the researchers.

    As I browse through the list of projects around the world at the various Microsoft Research facilities, it’s an interesting mix of somewhat practical ideas with pure research into areas that may never become projects. One thing is clear, and that’s much of this work involves large amount of data. Quite a few of the projects themselves deal with data issues, from searching to visualization to analytics. I have to think a few of them will influence or impact SQL Server over the next decade in some way.

    Steve Jones

    The Voice of the DBA Podcasts

    We publish three versions of the podcast each day for you to enjoy.

  • The DBA Office

    This is a great office.
    This is a great office.

    I’ve written about offices I like in the past. I’ve worked in a variety of offices, and having telecommuted for the last decade, I find that I mostly prefer a variety of environments. I have a standing desk, where I do most of my work, but I often find myself moving to another room with my laptop to work in a quieter, or louder, environment. I work at a coffee shop, in hotels, even in the car at times. It seems like I might be working too much, but I think I have a good balance between life and work. I just find myself working for short stretches in very disparate environments as I wander through life.

    For me, the ideal environment has varied according to the job that I did. Software development seems to require more quiet and separation than operational work. The more I coordinate with others, the more I like an open floor plan. The more I have to concentrate on my own work, the more I prefer a peaceful, solitary environment. As a DBA, I’ve had to work in both environments and I’ve had my own office, a shared office, a hot desk, and an open plan. I often haven’t had a choice of the arrangement in most jobs, so it’s a good thing I’m adaptable.

    I ran across a piece that looks at the history of the open and closed office, as well as different ways or organizing desks. There are great pros and cons in the article for each setup, and the compromises people make. This week, I’m wondering what many of you would like your arrangement to be.

    What would be your ideal office work environment?

    Would you prefer an open plan? A closed office? A hot desk arrangement that incorporates both of these? Do you want public spaces at times and private locations where you can get solo work done if you need it? If you have preferences, or comments about your current setup, let us know today. Maybe we can design a few “ideal” office spaces together.

    Steve Jones

    The Voice of the DBA Podcasts

    We publish three versions of the podcast each day for you to enjoy.

  • Double Compliance

    hipaa_compliant_seal    vs          pci-seal

    I haven’t ever been bound by HIPAA or PCI regulations with the data I’ve managed. Those laws hadn’t been enacted when I worked in those industries, and so I’ve never had to go through an audit. I have been through ISO 9000 and SOX audits, and I found those audits to be both a pain and also a good idea. Various inconsistencies and exceptions in our policies were found, often strengthening our security or bringing more consistency (and stability) to our organization. Those two audits were also very close in scope and requirements. If we could pass one, we typically could pass the other.

    However PCI and HIPAA are not the same, and you shouldn’t expect that passing one would mean you could pass the other. For most of us, we wouldn’t be bound by both of these, since they are applied to the financial and medical fields respectively. However as we look to move forward and use new partners in business, including cloud services, we should be aware that just because a company has one certification doesn’t mean they have the other. If your business partner is PCI complaint in some way, I wouldn’t assume that this means they are in any way HIPAA compliant, and vice versa.

    Should we have standards for data protection that matter to a variety of industries? I’m not sure we should, despite the hassles that may mean for those of us bound by these regulations. Each industry and type of business has it’s own requirements, some of which are not applicable to other fields. Trying to build one standard for privacy, security, or any other requirement is likely to mean a watered-down, ill-fitting regulation that doesn’t protect any data well. Instead we should have specific requirements we need to meet to provide security (or any other need), without specifics on the technology or implementation used.

    Most of you probably don’t like the idea of any regulation, and I’d like to agree with you. However I’ve seen too many people ignore good practices, engage in morally debatable activities, and in general treat other people, and data, in a way they wouldn’t want to be treated themselves. A little regulation, that limits abuses and gross malpractices is a good thing. Too much regulation, specifying details that are often obsolete before they can be enforced, is a bad idea.

    Steve Jones

    The Voice of the DBA Podcasts

    We publish three versions of the podcast each day for you to enjoy.