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

Let's Not Mess Around with Security on our Personal Systems Either!

Essential Security Practices for Your Personal Systems Ensuring a minimal level of cybersecurity, privacy, and availability on your personal systems means you need to manage the following essential practices. This is a brief overview of recommendations from sources like CISA, NSA, etc., focused on personal laptop, phone, and other systems' security. Anti-virus  I've found you'll get the best anti-virus protection and usability from a paid product - I've always had good luck with Norton labeled products. If you are looking for current vendor offerings see:  https://www.pcmag.com/picks/the-best-antivirus-protection Regardless of whether you choose to use a commercial product or open-source anti-virus tool, it is absolutely something you need to use. This is the minimally needed level of system security. Once installed, ideally, it should be invisible until there's a security problem it can't prevent or solve.   Backups You need to have at least a minimal level of ...
Post a Comment
Read more

RACI, Cybersecurity and NICE Framework

The NICE framework from a RACI point of view The NICE framework ( NIST SP 800-181 rev. 1) established a standard approach for describing cybersecurity work, in order to help stakeholders share a common language and ideally improve how to identify, recruit, develop and retain talent. It breaks down cybersecurity work role categories into: Oversight and Governance; Design and Development; Implementation and Operation; Protection and Defense; Investigation.  Which is very cybersecurity-centric and not related to common tools for project management within companies. Especially smaller enterprises that do not have dedicated people to mange and coordinate cybersecurity needs. A  RACI chart  is   a project management tool used to define and clarify roles and responsibilities within a project team.   It stands for Responsible, Accountable, Consulted, and Informed, and visually represents who is responsible for what, who is accountable for the outcome, who needs to be c...
Post a Comment
Read more

Typescript - It might not be easier, but but it's surely different

Typescript is a statically typed language, that is a superset of JavaScript. I've had the discussions and debates about that aspect of the language. I am all for static typing. Any way my tools can help me be better is alright by me. So I avoid the ' any ' type designation and make sure I have guards on ' unknown ' types, as much as I can.  Any  does not carry any useful type information, while unknown does, and allows it to enforce type checking.  Anything can be assigned to a variable of type unknown , but an unknown value cannot be assigned to variables of other types without explicit type assertion or narrowing. Similarly, no operations are permitted on an unknown value until its type is refined. This behavior ensures type safety and prevents runtime errors. (Refined with help from google). I bring this up because I was arguing with the compiler recently because I'd assumed both made no use on any type information in any circumstance - because I haven't ...
Post a Comment
Read more