Category: Editorial

  • Bad Days

    We all have them. As DBAs, there could be many bad days in our career. We poke fun at one of them with our first humorous DBA Team story this year. Hopefully you enjoy that one and smile. I know I got a kick out of reading it when got the first draft.

    However that’s not a really bad day for me. I’ve had some bad days at work involving corruption, missing backups, hardware failures, viruses, and more. Typically they involve fewer car crashes and political games than the DBA Team deals with, but they’re almost as stressful and more than a few have stretched well into the night.

    This week, I’d like to commiserate with you. I’d like to hear about the hard stories that you can now look back on with a smile (or grimace), having managed to move beyond the situation.

    What’s been a really bad day in your DBA career?

    Or perhaps you’ve got a bad development story, an administrator story or something else. What was a time when you thought your career might be over, or you might lose your job? When did you feel a high level of stress over a situation that you thought might overwhelm you? Was there a time you might leave this industry?

    I’m not looking to bring up bad memories, and please remember to be professional with your stories. However I’ve found writing things down can be cathartic. Perhaps you’ve held onto some anxiety for years, or fear about a repeat. Perhaps a little sharing, and empathy from the community, will help you feel better about the situation.

    As always, if you’d like to share anonymously, feel free to send a note to sjones at this domain and I’ll post your story without your name.

    Steve Jones

    The Voice of the DBA Podcast

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

    The Voice of the DBA podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.

  • Privacy and Data

    Privacy. Security. Encryption. Protection. Responsibility.

    All big words, with many connotations. Unfortunately, the meanings behind the words seem to be dwarfed by one other word: profit. Data brokers and even departments inside various organizations make a lot of money from their data, and I don’t expect they’ll want to see that stop anytime soon.

    So much of our data is being collected, sold, and (arguably) poorly secured. Citizens are complaining and governments are taking some notice. The US Congress has a committee investigating how some of the large data brokers are handling data. The committee compiling the report doesn’t have much power, and I’m not convinced that much will change, regardless of the conclusions they reach.

    However I do think that those of us that work as data professionals should be aware that we may find ourselves bound by new rules and regulations over time. I wouldn’t think anyone would preemptively prepare for more control by changing their systems or processes, but I would expect that data professionals might want to ensure they understand how their data is being handled and secured, just in case anyone asks.

    Steve Jones

    The Voice of the DBA Podcast

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

    The Voice of the DBA podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.

  • The Worst Code

    This piece was written awhile ago by Jeff Atwood, but I saw a mention about it recently. It’s about software developers hating software. It’s a fun piece, and written a bit tongue-in-cheek, though with a lot of truth in there. Certainly lots of the “bundled software” that come with gadgets is unnecessary and poorly tested. That’s sad, as there is the chance to add value to products if the software is well written, and perhaps, open sourced.

    However the thing that caught my eye was the ending. Mr. Atwood says that if a developer in an interview doesn’t say the worst code they’ve seen lately is their own, then they may not be a competent developer. I hope that part is also a joke, and I suspect it is. Though I also think that it’s a healthy attitude for people to see room for improvement in most of their endeavors.

    No matter what type of task you are performing, and certainly programming is an area many of us focus, complacency is a poor way to approach your work. We know we won’t be perfect, we know we’ll make mistakes, we know there’s room for improvement, and we know we NEED TO GET THE PROJECT DONE. The balance we strike in moving forward should be accomplishing tasks, learning what we did right and wrong, doing more of the former (and less of the latter) in the future, all while taking pride in the work we do well.

    Certainly some people are obsessive and perfectionists. There’s probably another few choice words some of you have for those individuals, but most of us need to balance our desire to build something amazing, with the necessity of completing work. We also need those little wins that come from having our work solve problems, even if we’d build software better the next time. The important thing is that you try to do better the next time.

    Steve Jones

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

    The Voice of the DBA podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.

  • How Many Passwords?

    How many user names and passwords do you have? If you’re like me, you have a lot of them. Actually I don’t have too many user names, sticking with “Steve Jones”, “sjones” or my well known “way0utwest” for my logins. However I do try to have as many passwords as I have logins. Using my Password Safe utility, I count 265 items in my personal safe and 176 in my business one. Some of those are old and dead, but quite a few of them I use on a regular basis.That’s similar to what Keith Combs notes in his blog post on IDs and passwords. He has 172, though I’m sure that number has crept up since he wrote the post. The piece links over to a few identity discussions from others at Microsoft that are trying to make identifying users and managing security easier. In the Microsoft world I think that works well, but the larger world outside of Microsoft software requires a bit more work for most of us.

    The original piece was written awhile back, and since that time, I’ve come to find that more and more of my logins are authorization links from one of the large companies (Microsoft, Google, Facebook, Twitter), with some sort of token that allows me to login. I have my Live account working on a number of Microsoft based services, but my Google account crossing their platform to Gravitar and StackExchange. My Twitter and Facebook accounts are linked to a few places, though I’m careful about which one of those I link to which application or service.
    Using passwords, moving to application links from a platform, and even now adding two factor authentication with a mobile phone makes me think that we are not necessarily finding a better way of managing authentication. Perhaps we are making things much more complex without creating any more security.

    I don’t know what the future will bring, but I suspect that many of our current methods of providing security will prove to be inadequate. I’m hoping that we find out on some services like Funny or Die or ESPN, and not because people find ways to jump from external applications to internal servers like Exchange or SQL Server.Steve Jones

    The Voice of the DBA Podcast

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

    The Voice of the DBA podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.