Since the original came out, I have made updates here and there, and added references to some newer material.

You could see "EU CRA: It's Later Than You Think, Time to Engineer Up!" https://nxdomain.no/~peter/eu_cra_its_later_than_you_think_time_to_engineer_up.html as a further development in response to the real world (or at least the EU parts) moving forward.

@pitrh

One important aspect /all/ people overlook, including you:

Aircraft carriers are /simple/ compared to software.

Building a modern air-craft carrier takes merely one million different stock-numbers.

/bin/bash is 200k lines

Last I looked SystemD was north of 1M

All of FreeBSD is 26 million lines.

Linux kernel alone is 36 million lines.

Ohh, and also this old rule of thumb:

"Well written code typically has one bug for every thousand lines."

@phloggen @pitrh that seems like the least useful comparison ever.

All rivets will have the same stock number, all blank lines between functions are counted separately.

I assume there's at least one computer running one piece of software on an aircraft carrier in a critical role. It probably doesn't even have a stock number separate from whatever it's running on.

Seriously, this comparison is amazing in its ridiculousness. Well trolled.

@gabe @pitrh

I can see how you might think so, if the only big projects you have been involved in were software.

To people who have done big projects outside software, 1 million SKU's is a LOT - because it is.

Very few people have tried both, so almost nobody realizes how many orders of magnitude software is more complex than anything else.

@gabe @pitrh

You should tell that to people who actually build air craft carriers, but more importantly, you should listen to them.