|
|
|
|
|
by alert0
1838 days ago
|
|
I would really like to see a move toward purpose built systems and actually software engineering. General purpose operating systems really speed up development time, but I am not sure we need critical infrastructure to be capable of playing Doom or running generic ransomware. In the same vein, it would be nice for the people who built these systems to be able to provide tolerances and document failure cases. This would be mandating memory safe languages, understanding dependencies, mandatory penetration tests, mandatory fuzz testing. We have standards for building bridges but not for computing systems. Another policy point would be data de-risking. It has been shown time and time again that companies cannot protect their own data, not to mention user data. I think we should make it very costly to be breached and lose PII. It would raise the bar a lot for who could do what, but I do not think companies have really demonstrated that they can handle this data responsibly. These data losses have even become a national security risk. [1] 1. https://foreignpolicy.com/2020/12/21/china-stolen-us-data-ex... |
|
We've tried bespoke systems for all sorts of components. That's how we end up with multi-billion, multi-year sole source contracts where $beltwaybandit prints money and it takes multiple years to support now-common functionality/capabilities because it wasn't in the initial meticulously-specified, waterfall-driven design plan enshrined in the contract 5 years ago. And that contract itself was an extension to an extension to an extension from a contract a decade before that.
Excuse me, I'm having flashbacks now.