Skip to main content

It's all broken...

So, Scott Hanselman struck a chord again: Everything's broken and nobody's upset. The worst part is I can see that I'm part of the problem on both sides. I've excused many problems with software - shrugging as I restart the software or reboot. I save my anger for those occasions where I fell I've lost serious work and substantial time. Other than that I accept problems, glitches, crashes as "the cost of doing business". I believe it's actually because I've amused myself and earned a living creating software, that I am able to accept what's often pitiable quality. I've spent time working on systems that are not much more than breadboards with wires cascading from it, where getting something, anything to work was a huge accomplishment.

But that was then and this is now. No way would I put up with a car that suffers from numerous small problems as today's software can. And putting these two thoughts together, it's now frightening to think of the amount of software a car depends on....

I think I need to raise my standards all the way around, expect more from the software I use and expect more of the software I produce. And I guess I'm not alone in that.
Labels:

Comments

BenJammin' said…
You're not. The guys at Fiat-Chrystler know your pain : https://www.google.com/url?sa=t&source=web&rct=j&url=http://www.wired.com/2015/07/hackers-remotely-kill-jeep-highway/&ved=0CBwQFjAAahUKEwiw_7b0pbHHAhVMoYAKHWPOC_Q&usg=AFQjCNEljldATkVjYn6pyzjOSzxEQylpCg&sig2=YCB0IlJ7GFmdH3jMU9EXgg
7:46 PM
BenJammin' said…
You're not. The guys at Fiat-Chrystler know your pain : https://www.google.com/url?sa=t&source=web&rct=j&url=http://www.wired.com/2015/07/hackers-remotely-kill-jeep-highway/&ved=0CBwQFjAAahUKEwiw_7b0pbHHAhVMoYAKHWPOC_Q&usg=AFQjCNEljldATkVjYn6pyzjOSzxEQylpCg&sig2=YCB0IlJ7GFmdH3jMU9EXgg
7:47 PM
Post a Comment

Popular posts from this blog

Unit Testing - What to Test

This I wrote to answer a question that came up when we were discussing our software process and I was training developers on how to unit test. It seems a simple enough question, but I kept pondering it and delving deeper until I realized I needed to write this monograph. What unit tests should we write? How do we know what to test? Ideally, unit tests should cover every path through the code. It should be your chance to see every path through your code works as expected and as needed. If you are practicing Test Driven Development then it's implied everything gets a test. In the real world, you might not be allowed to test everything - for instance, if the testing suite ends up taking a week to run, then the world will have changed by the time it finishes and the test results will be obsolete. Unit testing at it's basic is testing an object, a method - the smallest unit of your code that it can test independently. It should test the inputs "goes into" an
Post a Comment
Read more

Healthcare and Health Informatics Glossary

Here is a glossary of terms useful in Healthcare and Health Informatics ACO (Accountable Care Organization) MEDICARE’s outcomes-based contracting approach Arden Syntax an approach to specifying medical knowledge and clinical decision support rules in a form that is independent of any EHR and thus sharable across hospitals ARRA (American Recovery and Reconstruction Act) the Obama administration’s 2009 economic stimulus bill Blue Button an ASCII text based standard for heath information sharing first introduced by the Veteran’s Administration to facilitate access to records stored in VistA by their patients. The newer Blue Button + format provides both human and machine readable formats. CCD (Continuity of Care Document) an XML-based patient summary based on the CDA architecture CCOW (Clinical Context Object Workshop) an HL7 standard for synchronizing and coordinating applications to automatically follow the patient, user (and other) contexts to allow the clinical u
2 comments
Read more

Files as UI

Files as UI vs API  -  compares attributes of iCloud vs Dropbox. It starts on an interesting note - the model of a file system in the UI is dying, and should be let go. Beyond that it looks at mappings of each system to a file system from an API point of view and compares the successes of each. I find the initial thread the most interesting. Drop the mental model of a file system - which maps virtual concepts of files and directories to a physical model of papers, folders and file cabinets - and replace it with...what? This is a paradigm shift for me. I have to admit, I loath, hate, nay, despise looking for things. If I can't find something easily, it's only about a minute before I start growling and muttering things my mother would disapprove of. On this basis, I like the idea that I can save myself from thinking about where to put things or, where I have already put them. But how do we do this? It's non-trivial, since humans think of "things" and once they
2 comments
Read more