We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Much software is now provided as a service and is typically deployed continuously (CD, continuous deployment), surrounded by enough automated testing (CI, continuous integration) that we can be reasonably sure that a new revision is likely to at least work to some extent.
In contrast, there is a world where people do not appreciate such continuous changes with only a likelihood of things working. Software that controls nuclear power plants, elections, pacemakers, airplanes, bridges, heavy machinery — stuff that can kill you if it does the wrong thing. These fields appreciate software sticking around for decades, with well described and pre-announced changes.
The presentation consisted of a generic part on long term software development and a specific critique of their software development so far. For the generic part, I asked my friends on Mastodon to weigh in:
Mastodon delivered in spades, and most of this post is derived from the input from kind Mastodonians. Now, nothing that follows is particularly earth-shattering. However, the strength of certain recommendations is noteworthy.
continue reading on berthub.eu
⚠️ This post links to an external website. ⚠️
If this post was enjoyable or useful for you, please share it! If you have comments, questions, or feedback, you can email my personal email. To get new posts, subscribe use the RSS feed.