Voice of the DBA

Category: Editorial

  • The Career Bucket List

    The Bucket List is a fun movie to watch, where two old men get a second chance at life and engage in some activities they’ve always wanted to enjoy. The idea of a bucket list isn’t new, and there are plenty of sites that can help you manage one. Brent Ozar has one on his site that he calls his Epic Life Quest, and I’ve enjoyed watching him tick off items. I got the idea of my own list nearly 20 years ago after hearing Ted Lesonis on the radio. He had a list of 101 things to tackled in life. Since he sold his stake in AOL, he’s had the resources to work on them. I have one, along with my wife, and we’ve worked through a few items over the years, though we were talking recently we need to revisit the list and perhaps revise things.
    Why revise a bucket list? One of the things I’ve learned over time is that I change and the values, goals, and desires I once had will also change. The things I’ve had put on a list at 20 years old would have included owning a Ferrari, a Porsche, and a Lamborghini. At 40+, having owned a Porsche, the other things seem a little silly and vain, not to mention very impractical. At this point in my life, there are other things I find more interesting and captivating. The bucket list of today would be more experience based and likely contain more volunteer oriented goals.
    I think my career has really changed as well, and as I move towards retirement, I don’t know if there are many more goals for me in this area.  However, if I think back, I know I’d have had lots of them when I were younger. There are a few things I’d still like to accomplish, and hopefully I’ll find some time to work on them. For now, I wanted to ask you about your career.
    What’s your career bucket list? Is there something you’d want to accomplish? Build some software? Work in an industry? Get a particular job, position, or work in a location? Maybe you’d like to become an advanced techie on some platform or using some technology. There might even be a goal you have to achieve some recognition for your skills.
    This is a tough question to spring on you in an editorial, but leave a comment if something comes to mind. If it does, maybe you want to jot some notes down that might help you move towards that goal. Even if nothing strikes you, perhaps you want to bookmark this piece and spend some time in the coming weeks thinking about your career. Goals are always good, and they can help drive us in a direction that may ultimately provide some meaning or satisfaction that is lacking.
    Steve Jones

    The Voice of the DBA Podcast

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

  • The Downsides of AI

    I remember reading about AI as a college student, and I always wondered if we’d get computing algorithms that might actually make better decisions than informed humans. As my tech career grew, I saw the advancement in systems, like Deep Blue, that showed we could build better systems that might beat humans at their own games. The recent success of AlphaGo makes me wonder what the next challenge will be?

    Certainly machine learning (ML) and AI-like systems are becoming quite popular in business these days. More and more companies are trying to find ways to use these computer science tools to improve their organizations capabilities. Whether these techniques will continue to be popular remains to be seen, but in the short term, all the efforts of companies like Microsoft and Amazon will get many companies to try to build intelligent systems.

    There is a lot of data being used to fuel these AI and ML applications, so it’s a natural fit that many data professionals will want to be involved. It’s a complex area, where lots of data is used to conduct lots and lots of experiments. That type of work my not suit many of you, but give it a try on one of these platforms and see what you think. Perhaps this is work you will enjoy. However, even if you enjoy the work and become good at it, there’s potentially some issue that may impact the use of these systems.

    We don’t know how most of the applications actually work. That’s because we haven’t programmed them. In some sense, many of these systems learn from data, and with a little guidance, but there isn’t necessarily a debug log that might explain all the actions. That is perhaps the dark secret of AI. We don’t really understand what’s going on.

    The article linked above looks at autonomous cars, which a number of companies are researching and building. One of the issues with the complex system(s) that runs the car is that we don’t necessarily know how it works. This might not bother technical people, but it certainly does bother many people. When there is a problem, and there will be a problem since there are always failures, how do we determine what went wrong and make it better? Add more data and retrain the system? I’m not sure that is a solution that most people will accept.

    Ultimately I think some of the research and work on AI needs to focus on allowing the model to output a set of data on what data is being weighed and the impact on the flow of information that leads to a decision. I know this is a tremendous amount of data, but it is probably the type of analysis that is needed for accountability in these systems. After all, it’s not just cars where this matters. Imagine that your have an AI system that cuts off all AC in the summer, or decides not to order enough resources for a busy time period. How do we explain to management that “the system just decided” on that course of action? I really think we need better tools for analyzing these models.

    Steve Jones

    The Voice of the DBA Podcast

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

  • Use More Pull Requests

    I noticed a short while back that Books Online is on github. You can fork the code and make corrections to pages and then submit a pull request. This is the model that many OSS projects use, including the amazing DBATools project. That one I really like, and if I was better at PowerShell, I’d contribute. If you’re a PoSh whiz, I’d urge you to contribute.

    A few years ago I saw a lot of complaints about the SQL Saturday site, and over the years I’ve also seen a number of complaints about the Pass Summit sites, and the registration process. At one point there was a debate over whether PASS should build a registration system or continue to pay for the service. To me, this was a perfect place to start a project, maybe with a few volunteers, and then crowdsource enhancements and improvements. Get help from the members of this technical community, after all, this is the way most of us make a living.

    If Microsoft can get help from outside, I’d expect other organizations could as well. Certainly PASS has limited resources, and this is a great way to perhaps get new ideas, innovate, and grow their system. There will be some friction and loss in reviewing changes, but I’d expect that the overall gain would come from the greater number of people contributing to the software.

    We’ve kicked this around for SQLServerCentral and Database Weekly, and I am hoping to start getting help in enhancing my own site from its community at some point. There are certainly challenges and difficulties in integrating code from lots of sources. DevOps makes this easier, with more automation to evaluate and test code before a human needs to review it. However, DevOps has its own challenges, with extending the culture and process to others, and finding those individuals that want to contribute and buy into the philosophy, not to mention maintaining code quality and standards. However, I hope that you consider using pull requests and getting help from others in your own organization or project.

    Steve Jones

    The Voice of the DBA Podcast

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

  • Jumping Ahead

    While on vacation recently, I went to see Spider-Man Homecoming with my family. It was an enjoyable movie on a rainy afternoon, and a nice addition to the Marvel lineup. I think this actually might be my favorite Spider-man movie, and I’d recommend you watch it if you enjoy this genre. It was humorous, well written, and some nice special effects. As with any of these Marvel movies, you definitely need some suspension of disbelief, especially with the technology.

    In the movie, Peter Parker is anxious to join the Avengers and become a full time super hero, going on missions that have a large impact in the world. He chafes as the idea that he needs to stay in school and let his life progress at a more normal pace, which Tony Stark seems intent on pushing. Many of us have felt the same chafing in our own youth, wanting to get out of school, go to work, and move on in life.

    However, even in our careers, I find people wanting to jump forward, moving to new technologies and platforms as quick as possible. I certainly see this in the SQL Server world, often from developers, that want to find the holy grail of database storage in CouchDB, CosmosDB, Neo4J, etc. I’ve often seen this in the development world with different types of technologies, such as web frameworks. Maybe we in the data space are more conservative? Or we like sticking to what we know works well?

    We data professionals are not immune from the desire to jump ahead. I see plenty of data people wanting to jump into some new area to grow their careers. Data Science ( and AI, Machine Learning, etc.) is the newest craze, with quite a few people learning some R, some model training, and wanting to find a use for their skills. Or maybe an employer, preferably one that pays more than they make now. Good luck to you, but I’d encourage you to remember that good data science takes lots of skill, knowledge, and practice. I wouldn’t expect a quick jump into this new area.

    There are certainly other changes in the data world, such as the graph capabilities coming to SQL Server 2017 and the explosion of cloud database implementations. However, don’t get caught up in expecting quick changes in your job or your income. Continue to learn, experiment, build a POC and practice your skills. Change usually comes for most of us at measured paces. This pace is hard to accept if you don’t have the habit of regularly learning something and applying it in small doses, understanding that not everything you learn will be useful (or used) in your current situation.

    Steve Jones

    The Voice of the DBA Podcast

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