this post was submitted on 15 Feb 2026
0 points (NaN% liked)

Software Engineering

450 readers
1 users here now

Software Engineering is the systematic and engineered development of software in all its life cycle.


Rules

  1. Keep related to software engineering
  2. Keep comments on-topic of the post
  3. Try to post free/open access content
  4. Try to post content from reliable sources (ACM, IEEE, SEI, NN/G, ...), or useful content in general
  5. Relevant questions are welcone, as long they are genuine and respectful
  6. Be genuinely respectful, kind, helpful; act in and assume good faith
  7. No discrimination
  8. No personal attacks, no personal questions
  9. No attention stealing: no ads, spam, influencers influencing, memes, trolling, emotional manipulation/advertising (e.g. engagement through enragement or other negative emotions), jokes that dissipate the focus of the topic, ...

Resources

founded 3 years ago
MODERATORS
 

Explaining why we need "apocalypse-proof software" and some actual software tools for the mentioned situation.

you are viewing a single comment's thread
view the rest of the comments
[–] somegeek@programming.dev 0 points 1 month ago

You're absolutely right. Note that I said "years without updating" not "never updated". Depending on the domain, I think we can always at least aim to make our software as rugged as possible.

I think we should take more aspiration from mechanical engineers and car manufacturers.

A car needs maintenance, but you might just start up a 70 year old engine and it works ok. Our a 70 year old car might be still up and running with minimal maintenance. You don't want to be rapairing/updating your car every month or week.

I understand the domains are different, but how much really? I think if we build with the "rugged" mindset and good engineering, there is a lot of improvement to be made to what software is.