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

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

Risk Mitigations for Custom Applications

  In many healthcare applications, often due to the cloistered nature of the use cases – e.g. it will only be accessed by users authorized in a particular facility, such as an operating room suite – the needs for Authentication and Authorization are minimized when the system is designed and implemented. This presents a risk as soon as you allow for the possibility of users with ill-intent or that otherwise want to operate outside their given roles. Custom applications need to consider these possibilities and implement the following measure to ensure the integrity of the system. 1.   Authentication and Authorization Controls: Multi-Factor Authentication (MFA): Implement MFA for all user logins. This adds an extra layer of security beyond just a username and password. Role-Based Access Control (RBAC): Grant users access only to the data and functionalities they need for their specific role. This minimizes the potential for unauthorized access. Strong Password Policies: ...
Post a Comment
Read more

You don't really know who you're talking to online...

The following is a story that I think highlights the assumptions that get you into trouble online... https://www.proofpoint.com/us/blog/threat-insight/i-knew-you-were-trouble-ta456-targets-defense-contractor-alluring-social-media This is particularly scary since we found so much utility in online connections during the pandemic and out of necessity, started trusting more online. Please note the timeline for this breach - it was a long, slow process, a key factor in many 'cons'. "Build trust" is a key first step, once someone has identified you as a party. You think...you're convinced you know who your talking to, but if you don't triangulate the identity with some non-online, ideally in-person information, you shouldn't trust. And even if you do get what seems like real-life confirmations of identity, you must look at questioning motives, needs, and keeping danger at arms-length. Online includes email, texting (sms), application chatbots, voice communicati...
Post a Comment
Read more