Voice of the DBA

Category: Editorial

  • Job Worries over Automation

    There was a report recently where the NSA noted that they are reducing the number of system administrators by 90%. If the report is true, that would certainly worry many of the people in the technology industry. However I’m not sure that the quote given in the article means what it looks like at first.
    Much of the technology reports that we see aren’t completely true since many of the reporters aren’t that familiar with the details of how computer technology works. In this case, however, we have a quote: “What we’re in the process of doing – not fast enough – is reducing our system administrators by about 90 percent,” It might be hard to interpret this remark in any way other than the NSA is looking to reduce the number of people, but if you read further, the piece notes that the NSA is concerned about contractors, not necessarily FTEs. I suspect that any reduction in contractors employed by other companies will be made up by increased internal headcount.
    However even if the NSA can reduce the number of people needed to administer their systems, I’d suspect that means that they had too many people to begin with. The various reports of this story all talk about automation being used increasingly to handle the load of system work, but the idea that automation replaces people is a myth. Automation usually results in less growth of people, but rarely a reduction in staff.
    I’ve heard the concerns over automation replacing technology workers for decades (literally) and I’ve yet to see it happen. We have more technology workers than ever before, and no sign of there being less in the future. Your department might change, you might hire less, but there will be lots of jobs in technology for the foreseeable future. In other departments that might not be the case, but I bet you we’ll have system administrators, DBAs, and developers for a long, long time in most companies that have them today.
    Steve Jones

    Video and Audio versions

    Today’s 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.

    Follow Steve Jones on Twitter to find links and database related items and announcements.
    Steve Jones Windows Media Video ( 16.4MB) feed

    MP4 iPod Video ( 19.1MB) feed

    MP3 Audio ( 4.0MB) feed

    Feeds are available at iTunes and Mevio

    To submit an article, rant or editorial,
    log in to the Contribution Center

  • Sensors and Data

    The programmable world. It’s an interesting concept, but not one in which we have extremely detailed specifications and strongly bound software systems that must be built to interact with each other. I think many of us have assumed that’s how we would enable the further computerization of our physical world. As an example, we’d have cars that communicated with the road, with other cars, with semi-central authority(ies) that might be managing our interactions, all of the infrastructure pre-built.

    However that isn’t necessarily what will happen. In this O’Reilly piece, the author notes cheap sensors can read the color of lights in the same way that humans or my Lego Mindstorm can detect color. Traffic sensors need not communicate with cars; these sensors could instead just identify cars and count them, measuring their speed and adjusting traffic lights based on actual conditions. Imagine the future when more and more sensors gather their own data and make decisions.

    In a sense, this is how the Google self-driving car works. Rather than depend on infrastructure and external programming, the car gathers its own data and adjusts its behavior depending on the interpretation of the data. Whether or not you like the idea of self-driving cars (I do), the idea of an autonomous device acting based on programming and a large amount of data is a fascinating move forward in computing.

    I think this shows that data gathering, processing, and analysis will become a more important part of our future computing worlds. Some of this data will be transient and discarded, but lots will be stored. We’ll use data to ineract with the real world immediately, but we will also perform analysis later and reprogram our devices to operate better in the future. That means there will be new, and more, opportunities for those of us working with data.

    Steve Jones

    Video and Audio versions

    Today’s 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.

    Follow Steve Jones on Twitter to find links and database related items and announcements.
    Steve Jones Windows Media Video ( 16.5MB) feed

    MP4 iPod Video ( 20.0MB) feed

    MP3 Audio (4.0MB) feed

    Feeds are available at iTunes and Mevio

    To submit an article, rant or editorial,
    log in to the Contribution Center

  • If we can do it, so can you

    We hear constantly about the benefits, and potential pitfalls of cloud based applications. There are certainly reasons to move to the cloud, or stay away, depending on your particular situation and requirements. However one thing I hadn’t thought was viable was software development in the cloud. Most of the companies I’ve seen that host applications in the cloud still do the development on desktops and laptops, with a build server somewhere on site. However Microsoft wants to show us that this isn’t necessary.

    There is a push inside Microsoft to perform more of their development in the cloud. Across the last year or two, various managers inside Microsoft have been moving development to the cloud, typically starting with testing and code analysis. Those are great fits for cloud services, since they are used at discrete periods, but may requite lots of resources. One of the interesting things in the piece was that the first objectives was to speed up the continuous integration process. At Red Gate (my employer), we’ve seen a lot of benefits from implementing continuous integration, both in our applications and databases, and we’ve done a lot of work to smooth out those processes.

    Obviously Microsoft might have an advantage over many of our other companies in terms of Azure resources and cost, but I would bet the reliability is similar for their developers. If they can make it work, on products like Windows, SQL Server, Sharepoint and more, I’d think that many of us could make use of the platform as well. I know a few people that have worked with TFS on Azure, and they’ve been pleased with the performance and reliability. There are any number of other software services, like GitHub, that make use of distributed, cloud-based services for software development.

    However even if you don’t want to use the Azure platform, the idea of using virtual systems, of spinning up and down the machines you need to perform various functions makes lots of sense. You can make better use of your hardware resources, and even schedule continuous integration services (builds, tests, analysis) for different teams (or applications) at different times, improving your efficiency and not only speeding up your development processes, but hopefully improving the quality of the final code.

    Steve Jones

    Video and Audio versions

    Today’s 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.

    Follow Steve Jones on Twitter to find links and database related items and announcements.
    Steve Jones Windows Media Video ( 22.0MB) feed

    MP4 iPod Video ( 26.4MB) feed

    MP3 Audio ( 5.2MB) feed

    Feeds are available at iTunes and Mevio

    To submit an article, rant or editorial,
    log in to the Contribution Center

  • Risk and Assumptions

    Today’s editorial was originally released on Jan 22, 2009. It is being re-published as Steve is on vacation.

    I was reading Buck Woody’s blog the other day and he had a post on Risk where he quoted Warren Buffet: “Risk comes from not knowing what you’re doing.” I think that’s true and that’s part of the reason we’d had issues in our financial markets over the last couple of years. It’s also the reason that we have issues in many of the systems that we build.

    Often the people building IT systems go through an extensive evaluation to determine the needs and wants of their users. It’s an attempt to identify exactly what to build so that the user is pleased, a good estimation can be made, and everyone finishes the project happy.

    And that almost never happens.

    There are people that are better at this than others, but the overall state of the software development process is pretty poor. That means that any project you undertake, or that your customers or clients ask you to undertake is fraught with risk. I can see why there are plenty of people that don’t want to hire contractors to get software built, or that our management doesn’t want to start new projects with their IT departments.

    I don’t have a solution, and I’m not completely sure where the problems lie, but I do know that as the economy slows, people have less tolerance for risk. That means less IT projects, and potentially the need for less IT staff and contractors. Which then contributes to the slowdown of the economy as there are less people at work.

    If I were working in IT or consulting right now, I would be working to lower risk as much as possible. Adopting techniques that you are confident in, learning new skills and then applying them, even in side projects, can help grow your skills, increase the chances of projects being completed that the client is happy with, and keeping you employed. Now is the time to reassess the way you work, and find ways to show that you can work with your clients to meet their needs in an efficient manner.

    Efficient in their eyes, not yours.

    Steve Jones

    The Voice of the DBA Podcasts

    Everyday Jones

    The podcast feeds are now available atsqlservercentral.mevio.comto get better bandwidth and maybe a little more exposure :). Comments are definitely appreciated and wanted, and you can get feeds from there.

    Overall RSS Feed:  or now on iTunes! 

    Today’s 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.