Coding jobs and risk assessment

[Matty]

How many of our world's important life and death software infrastructure was coded by teams with members under the influence of alcohol etc?

Just think next time you get on a plane - the pilot's been tested but what about the developer who wrote the software telling the pilot of say the fuel levels?

Any complex machinery is only as strong as its weakest point....

[Derron]

These software things are not developed my one-man-shows. Also they are testing such software a bit more intense than your "my first calculator.exe"

Issue there might be the chain of used stuff ... each element adds to complexity and the possibility of a "bug/error/production problem".
Yet this is why test (scenarios) exist. Cannot take care of all eventualities but major cases and all "past accident cases" are surely taken care of.


bye
Ron

[col]

I started to ignore most of your posts when you were asking for and ignoring peoples advice but I'll bite this time...

How many of our world's important life and death software infrastructure was coded by teams with members under the influence of alcohol etc?

Zero.

There are VERY stringent coding guidelines for these types of systems. There are automated static code analysis software to check the code meets the guidelines before it's even compiled. There is a monitoring system checking if you steer outside the guidelines, and if you do, then something will be said by your line manager. There are many levels of code testing and checking. The same goes for the hardware too. There are multiple sensors getting the same information in case one is starting to give up, and multiple types of sensor doing the same thing - in case one type is affected by a certain type of technological interference - there are backups for the backups.

Anyway for the software it's very difficult to get something badly written accepted into production. If something negative does get through then there's a huge internal inquiry and people get disciplined/fired - in other words, software engineers that value their worth in their job don't write software under the influence of anything.

[GfK]

I started to ignore most of your posts when you were asking for and ignoring peoples advice but I'll bite this time...

How many of our world's important life and death software infrastructure was coded by teams with members under the influence of alcohol etc?

Zero.

There are VERY stringent coding guidelines for these types of systems. There are automated static code analysis software to check the code meets the guidelines before it's even compiled. There is a monitoring system checking if you steer outside the guidelines, and if you do, then something will be said by your line manager. There are many levels of code testing and checking. The same goes for the hardware too. There are multiple sensors getting the same information in case one is starting to give up, and multiple types of sensor doing the same thing - in case one type is affected by a certain type of technological interference - there are backups for the backups.

Anyway for the software it's very difficult to get something badly written accepted into production. If something negative does get through then there's a huge internal inquiry and people get disciplined/fired - in other words, software engineers that value their worth in their job don't write software under the influence of anything.

I've literally just put him on ignore - sick of reading his attention-seeking nonsense.  I'm all for a bit of bants but this is not that.  It's bullshit conspiracy theories - the sort of crap that leads to knobheads burning down 5G masts because they think that's where coronavirus is getting in.

[Qube]

@matty no more of these types of threads. First and last warning.