Category: Editorial

  • Auto DevOps

    As much as I like DevOps, this scares me. There are a lot of employees (20%) at BMW that are software engineers. They want to increase that to a larger percentage, which I assume means that we’ll have more and more code in our automobiles, with more systems tightly integrated. We’re even gathering more and more data in modern vehicles. Maybe there are good database job opportunities for some of you with automakers.

    If there’s one thing we’ve learned in a few decades of writing software, it’s that large monolithic systems are a mess. They contain vulnerabilities, and more importantly, they are very difficult to patch and change. All of the DevOps success stories I’ve seen from large systems have either been a complete rewrite, or a long term refactoring that removes dependencies and tight couplings between modules.

    In cars, we’ve seen all sorts of hacking issues. Hackers can attack a vehicle remotely and a faulty (or hacked) update might leave you in trouble. Granted these things aren’t that likely, yet, though I think this piece understates the potential problems. I think that because once a hack is discovered, how sure are we that a) it will be reported to vendors (hackers might just exploit it), or b) that a fix will certainly be developed that works well and doesn’t cause any issues (remember 10s of millions of lines of code current year cars), and c) consumers will apply the patch. That last item worries me, especially if cars become more connected and share data about operation or as we move to autonomous (semi- or total) vehicles.

    Personally I’m not against code in vehicles. I’m not even against some connected systems. What I am against is a monolithic, tightly coupled system. I don’t want engine control or drive by wire sharing a network or code with a CD player or navigation system. I don’t want one computer controlling vehicular functions, entertainment, and climate control. I also want to be sure that there is some protection for all this data, to be sure it doesn’t overwhelm any system. I’ll also admit I like idea of upgrading or replacing parts from different vendors, some of whom might do a much better job of building systems.

    We’ve learned a lot about software and complex systems. While I don’t want all manufacturers to use one system or have tight regulations, I would like to see some mandates that separate critical systems from each other. Both in code, and physically. We don’t need to specify code standards, or encryption, or any details, but let’s ensure that a base bar of building software is being used in any of the mass produced vehicles, planes, trains,  automobiles, or anything else of substantial size that is operated by the general public.

    Steve Jones

    The Voice of the DBA Podcast

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

  • A Summit Just North of The Big Easy

    I’m off today, traveling down to The Big Easy, New Orleans for a beignet. Well, not just a beignet, but also because I’ll be speaking at SQL Saturday #628 in Baton Rouge tomorrow. It’s easier, and more fun, to fly into New Orleans, so I’ll do that, have a quick snack at Cafe Dumonde and then drive up to Baton Rouge. It’s an easy, relaxing drive, and a nice (albeit warm) part of the country.  Hopefully I’ll arrive in time for a quick jog around University Lake.

    This is the 9th SQL Saturday for Baton Rouge, one of the oldest (they started with #17) and this is my fifth time going. I always enjoy the people and crowds down there and this is one of the largest SQL Saturday events in the country. The schedule has 12 tracks, and with over 500 people coming, they need that many to keep from having every room overcrowded. I have two sessions, and I’m looking forward to seeing quite a few others from other speakers, learning a bit more about SQL Server.

    I think it’s great that this event includes lots of developers from the area and covers a huge variety of topics. People come from all over the area, from Texas to West Florida, and sometimes from Arkansas and Tennesee. There is a wide variety of data related, and a few developer, sessions, as well as a nice career track. There is a huge thirst for knowledge, and for some reason SQL Saturday Baton Rouge on the campus of LSU attracts many people from all over.

    It’s great that we have people in our community that will put together a large event to help others improve their careers and get excited about databases and software. Holding an event like this takes a lot of work, and my hat is off to the organizers. They do a fantastic job and really put on a great event for everyone. I’m glad we have large events like this, and I also am glad we have people putting on smaller events all over the world. We have a fantastic SQL Server community, and it’s always a treat to get accepted to present. I hope to see some of you tomorrow and many more in the future.

    Steve Jones

    The Voice of the DBA Podcast

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

  • Who’s Smarter? Humans or AI Systems?

    I used to watch science fiction movies and imagine we’d have these incredible machines that could interact with humans in amazing ways. I always believed more in the helpful and useful AI in Star Wars than the dangerous systems of movies like The Terminator or The Matrix. I could even imagine a time when we have sentient systems, though I’m not sure they are coming anytime soon.

    I used to assume the Asimov’s Laws of Robotics would be implemented without any issue. After all, doesn’t everyone worry about security? These days I’m more cynical, and I wonder if anyone would actually bother to program limitations in a system. I expect more people would assume we’ll add in the laws later, once we know the other features are working.

    I do think we will get more and more systems like IBM’s Watson, that are designed to handle many tasks. When I read pieces like this one from HBR, I actually get a little worried. Not because machines will destroy humans, but they will greatly impact and change our society, potentially in disruptive ways for society. While we’ve seen issues with manufacturing over the years, there are still humans involved, and we have learned to find other jobs over time.

    The AI revolution, if that’s what’s happening, will occur quicker, and if the HBR piece is correct, will impact many more people, across a shorter period of time. Our economies and workforce may not adapt as quickly, which has a variety of economic implications for all of us, even those of us that might be secure in our positions. If we can teach systems to accomplish tasks at a level even close to what the average human can do, we might find ourselves either out of a job or working with some sort of robot.

    I don’t know how quickly we’ll advance, or even how far we will go, but I do find that the leverage offered by implementing advanced technology is certainly increasing in a way that worries me.

    Steve Jones

    The Voice of the DBA Podcast

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

  • Advancing Security

    One of the topics that is very important to many technology professionals is security. Security also might be one of the least understood aspects of our jobs. It’s an area that requires regular learning, monitoring, reactions, and vigilance. A healthy dose of paranoia makes a good security mindset, but this an easily devolve into greater stress and worry than might be appropriate, or the feeling that one should throw their hands in the air because of all the potential issues, attacks, and vulnerabilities.

    I think as individuals our part is to learn to write better code and scripts with security in mind, perhaps implementing best practices, but really the ways we will get better security is when vendors and platforms develop better ways to implement their security for us. They need people that study the issues and build fixes applicable to protect systems. This means we need good interfaces and basic contracts that ensure we can build software on top of platforms, but we will need to outsource this part of our security.

    Microsoft is one company that has been working to help us implement better security through defense in depth, through partnerships with other firms, and is making a difference. They’re not perfect, and there are still flaws in their software, but they are addressing and fixing them quicker and quicker. The world is changing, and Microsoft is a very different company than the one that build SQL Server 2008 R2, or even SQL Server 2012. They are maturing and becoming more responsive, and to me, more responsible about their place in the technology industry. They are striving to produce higher quality products, and when there are issues, they look to fix their mistakes quickly.

    Many of us that have struggled to believe in this new Microsoft and apply patches in a more timely manner. I’ll admit that I still rarely apply CUs unless I have a need for a fix, but mostly that’s because I don’t want any unexpected issues to crop up when I’m presenting and I don’t have time to test that regularly. Like you, I have multiple versions of SQL Server. I do catch up periodically, and I certainly try to apply Service Packs within a few weeks of release, if not sooner. As much as Windows updates can be annoying, this is more a matter of timing than concern over quality, and I do try to keep up with these.

    Will Microsoft and other vendors make mistakes with updates? Sure, sometimes there will be a patch that causes a problem with some, maybe many systems. However, we do need to grow and advance the security of our systems, which will always have vulnerabilities. Therefore, we need good quality updates from vendors like Microsoft, which I do think has happened. However, we also need customers to apply those patches. You can be slow and conservative, but don’t be negligent and try to avoid them completely. That makes the security situation worse for all of us.

    Steve Jones

    The Voice of the DBA Podcast

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