Live data from Hacker News

Software engineering lessons from RCAs of greatest disasters

anoopdixith.com

71–80 of 150 posts

Re: Software engineering lessons from RCAs of greatest disasters

#71

Earlier quoted context omitted.

In terms of engineering (QC, processes etc), modern day software industry is worse than almost any other industry out there. :-( And no, just plain complexity or fast-moving environment, is a factor but not the issue. It's that steps are skipped which are not skipped in other branches of engineering (eg. continous improvement of processes, learning from mistakes & implementing those. In software land: same mistakes m…

If you're making the same mistakes over and over again I think that says more about your company than it does about the software industry. My first job was at a major automotive manufacturer. Implementing half the procedures they had would slow down any software company 10X - just look at the state of most car infotainment systems. If something is safety critical, obviously this makes sense but the reality is 85% of…

GP was speaking in the general sense not about their company.

Re: Software engineering lessons from RCAs of greatest disasters

#72
post #67

Earlier quoted context omitted.

In any other field of engineering, the engineers are all trained and qualified. In software 'engineering', not so much.

This is exactly why I support "engineer" being a protected term, like Doctor. It should tell you that a certain level of training and qualification has been met, to the point that the engineer is responsible and accountable for the work they do and sign off on. Especially for things that affect safety. Many software engineers these days are often flying by the seat of their pants, moving quickly and breaking things.…

Are all "engineers" trained on human error, safety principles, and the like? The failures described in the article are precisely not software failures.

Re: Software engineering lessons from RCAs of greatest disasters

#73
post #11

I think the software industry itself has accumulated enough bugs over the past few decades. E.g. F-22 navigation system core dumps when crossing the international date line: https://medium.com/alfonsofuggetta-it/software-bug-halts-f-2... Loss of Mars probe due to metric-imperial conversion error I've a few of these myself (e.g. a misplaced decimal that made $12mil into $120mil), but sadly cannot devulge details.

In terms of engineering (QC, processes etc), modern day software industry is worse than almost any other industry out there. :-( And no, just plain complexity or fast-moving environment, is a factor but not the issue. It's that steps are skipped which are not skipped in other branches of engineering (eg. continous improvement of processes, learning from mistakes & implementing those. In software land: same mistakes m…

> In terms of engineering (QC, processes etc), modern day software industry is worse than almost any other industry out there. :-(

How do you know that?

Re: Software engineering lessons from RCAs of greatest disasters

#74
post #67

Earlier quoted context omitted.

In any other field of engineering, the engineers are all trained and qualified. In software 'engineering', not so much.

This is exactly why I support "engineer" being a protected term, like Doctor. It should tell you that a certain level of training and qualification has been met, to the point that the engineer is responsible and accountable for the work they do and sign off on. Especially for things that affect safety. Many software engineers these days are often flying by the seat of their pants, moving quickly and breaking things.…

> Thankfully this seems to largely be in places that aren't going to affect life or limb

I've seen Agile teams doing medical stuff using the latest hotness. Horrorshow.

I've also seen very, very clean software and firmware development at really small companies.

It's all over the place and you have to look inside to know what is going on. Though job advertisements sometimes can be pretty revealing.

Re: Software engineering lessons from RCAs of greatest disasters

#75
post #72

Earlier quoted context omitted.

This is exactly why I support "engineer" being a protected term, like Doctor. It should tell you that a certain level of training and qualification has been met, to the point that the engineer is responsible and accountable for the work they do and sign off on. Especially for things that affect safety. Many software engineers these days are often flying by the seat of their pants, moving quickly and breaking things.…

Are all "engineers" trained on human error, safety principles, and the like? The failures described in the article are precisely not software failures.

The important distinction is that engineers are professionally liable.

Re: Software engineering lessons from RCAs of greatest disasters

#76
post #73

Earlier quoted context omitted.

In terms of engineering (QC, processes etc), modern day software industry is worse than almost any other industry out there. :-( And no, just plain complexity or fast-moving environment, is a factor but not the issue. It's that steps are skipped which are not skipped in other branches of engineering (eg. continous improvement of processes, learning from mistakes & implementing those. In software land: same mistakes m…

> In terms of engineering (QC, processes etc), modern day software industry is worse than almost any other industry out there. :-( How do you know that?

Experience?

Re: Software engineering lessons from RCAs of greatest disasters

#77
post #67

Earlier quoted context omitted.

In any other field of engineering, the engineers are all trained and qualified. In software 'engineering', not so much.

This is exactly why I support "engineer" being a protected term, like Doctor. It should tell you that a certain level of training and qualification has been met, to the point that the engineer is responsible and accountable for the work they do and sign off on. Especially for things that affect safety. Many software engineers these days are often flying by the seat of their pants, moving quickly and breaking things.…

I'm curious how you think the word "Doctor" is protected.

Do you mean that History PhDs can't call themselves Doctors?

Or chiropractors can't pass themselves off as doctors?

Or you mean Doctor J was licensed to perform basketball bypass surgeries?

Or perhaps podiatrists can't deliver babies?

Re: Software engineering lessons from RCAs of greatest disasters

#79
post #73

Earlier quoted context omitted.

> In terms of engineering (QC, processes etc), modern day software industry is worse than almost any other industry out there. :-( How do you know that?

Experience?

On HN and reddit, experience doesn't count. Only reading about others experiences after they've been paid to write research experiences.

Re: Software engineering lessons from RCAs of greatest disasters

#80

Earlier quoted context omitted.

Experience?

On HN and reddit, experience doesn't count. Only reading about others experiences after they've been paid to write research experiences.

Don't forget to cite your sources! The nerds will rake you over the coals for not doing so.
Post reply on HN