5 ms·
While I laud the goals, I am skeptical of the ability to met them. I very much believe that there is an industry-wide crisis of terrible software, but I don't
by ChrisMarshallNY 4y ago
While I laud the goals, I am skeptical of the ability to met them.
I very much believe that there is an industry-wide crisis of terrible software, but I don't believe that it's practical to go directly from "garbage to gold." The path is long, and far from straight.
Best Practices are how engineering disciplines, throughout history, have achieved progress in Quality.
Currently, Best Practices aren't really a "thing," in software development, and it shows. People like Steve McConnell are not really respected, and a general culture of "move fast and break things" is still pervasive. Engineers flit around companies like mayflies, techniques and libraries come and go, and there's an enormous reliance on dependencies with very little vetting. We spend so much time, trying to perfect our tools, without trying to perfect ourselves.
Academics and theorists have been proposing languages, libraries, infrastructure, and management practices that are designed to change lead into gold for decades, yet it never seems to happen.
I have always been a fan of self-Discipline, and the apprenticeship model. That requires a lot of social infrastructure that does not currently exist. It's as old as human history, and absolutely proven to achieve results.
"In theory, there is no difference between theory and practice; while in practice, there is."
-Benjamin Brewster
"It is not enough to do your best; you must know what to do, and THEN do your best."
-W. Edwards Deming
"The significant problems we face cannot be solved by the same level of thinking that created them."
-Albert Einstein
"Everyone thinks of changing the world, but not one thinks of changing himself."
-Tolstoy
https://xkcd.com/2030/ https://xkcd.com/2030/
- zozbot234 4y ago> While I laud the goals, I am skeptical of the ability to met them. Let's start with the easiest part, and rewrite everything in Rust (or a comparably safe language). We'll need something like this anyway to give our software a workable semantics that's free of UB (at least wrt. the "safe" checked subset). Then we can work on the harder problem of using proof to establish that the unchecked parts do not invoke UB, and that intended specifications are not violated even in the "safe" parts.
- formerly_proven 4y agoTons of, if not most, "move fast and break things" software is written in safe languages, not C or C++.
- ChrisMarshallNY 4y agoThe tools shouldn't matter. A good engineer can use whatever tools are at hand, to achieve their ends, as long as they take a Disciplined approach, informed by industry Best Practices. Tools can help us to work faster, and abstract some of the "day to day" trivia, but, at the end of the day, we are still left with ourselves. If you want a lesson in limited tools, try working on embedded software. Embedded development systems often have languages that are incredibly dangerous, and extremely limited (It's not uncommon to be working in a subset of ANSI C). Good embedded engineers are usually trained in hardware practices, as opposed to CS ones. They understand the core fundamentals of what they are doing, so their work is not just rote. I know that it's an incredibly unpopular stance, but I don't see any alternate path to becoming a better engineer, other than through patience, practice, persistence, and Discipline.
- kungito 4y agoAre you saying C# and Java are safe languages or which ones did you have in mind?