Mr. Mossberg recently wrote his last column. He's retiring this year, and penned a look at some of the technology he's experienced in his lifetime. Reading over the piece brought back some nostalgic moments for me as I think about how the world has changed. He also notes that early in his career he wrote this sentence: "Personal computers are just too hard to use, and it isn’t your fault ". Now he says "Personal technology is usually pretty easy to use, and, if it’s not, it’s not your fault."
I agree with that, and one of the complaints I have with our industry. We haven't done a great job of actually considering users and building software that's not only intuitive and easy to use, but also gets easier over time. While I learned to appreciate the adaptation of some Office software that keeps the often used menu items displayed and remembers previous options I've used for features, I find this is the exception, not the rule. Our software is often in the face of the user, and I constantly bemoan the state of poorly written applications.
As we've moved to larger displays, and smaller displays, using touch, speech, and other methods of interacting with computing devices, building newer devices that look nothing like the computer of the past or even the computers of recent years gone by, we haven't necessarily made the computer fade into the background. The smartphone (and related car displays, tablets, etc.) have perhaps done one of the best jobs of integrating into our analog world, but the interfaces, displays, and certainly rendering of content overall has a long way to go. Plenty of that is our fault, we, the people who build applications.
I wonder if we'll reach Mr. Mossberg's vision of having most of our computing infrastructure fading into the background. Certainly reducing the need for cords and remembering to charge things will help. I look forward to the day when I have multiple pads built into my desk, my kitchen, my car, and more to just charge my devices when I set them down, so I don't need to think about power. I want connectivity to be just available, and I certainly want to be able to enlarge text easily, without zooming in and scrolling side to side as my eyes age.
The world may get better applications and infrastructure, and hopefully much better security. I certainly think it's possible, though not likely to be ubiquitous among all parts of the Internet. I doubt that for most of us choosing to work with technology as a career that we'll see computing fade away. We're too involved in the details, and hopefully excited by systems, to abstract ourselves too far away.
Have you ever wondered how much database mail you have sent in the past day or week? What about those database mail items that were not successfully sent. In this tip, Greg Larsen shows you how to review the database mail items that have been processed by SQL Server. More »
Squeeze maximum performance and efficiency from every T-SQL query you write or tune. Four leading experts take an in-depth look at T-SQL’s internal architecture and offer advanced practical techniques for optimizing response time and resource usage. Get your copy from Amazon today.
Yesterday's Question of the Day
(by Henrico Bekker):
When querying a CostmosDB through the DocumentDB API, to return only properties where the property exists and indicating if the property has been assigned a value, which syntax must preceed the property test/check in the WHERE clause?
Answer: select property from table WHERE IS_DEFINED(property)
The correct syntax to evaluate non-empty results must be checked with the function IS_DEFINED. IS_DEFINED can be used to return a boolean value as result for a specific test value eg, TRUE or FALSE.
This newsletter was sent to you because you signed up at SQLServerCentral.com.
Feel free to forward this to any colleagues that you think might be interested.
If you have received this email from a colleague, you can register to receive it here.