As you start trying to build something that looks like the puzzle, you realise that instead of the 1,000 pieces originally estimated for the puzzle, you're going to need 5,000, and the puzzle is actually in 3 dimensions not just 2, and also the puzzle needs to fit with another puzzle built by a different team of people who had no idea your puzzle needs to fit with them. Then you find out your puzzle pieces, that you borrowed from someone else, don't work as expected with put together with certain other pieces... :)
Your supposed to design a 4 lane bridge for a new interstate, you say sure that takes 6 months where do you want it?. After 3 months they decide where they want it and expect the design in 3 more months. You say, that's not going to happen I might be able to pull 5 months though.
So, assuming you know where it's going to be you start pulling in some overtime and get to work. After another month they say, we need a 6 lane bridge, after another they want to add a train. And 2 weeks before the deadline they decide on a tunnel. SO, you end up submitting a 6 lane bridge design that can't handle trains.
Which is why software is always late, and you don't hand them what they want.
However I think this is true of a lot of fields... some people just can't grok (and don't need to grok) how an automatic transmission in their car works. I'm particularly inept when it comes to the subtleties of art and music.
But a particularly relevant analogy that I use would be that you are working at a library. (That is: a library where you can check out books, not a software library.)
Not only do you have to write a good portion of these books, but you also have to read a lot of the books in the library, and at the very least you have to read the table of contents and/or index of most of those books.
In addition to this you have to be very good at keeping the library organized, and you have to coordinate with other staff members at the library.
Smaller systems are simply a shelf or two of books, larger systems can span several buildings.
I like this analogy because most everyone can relate to it, it gives a very real physical sense of size, and I think it pretty adequately describes what a programmer has to hold in their head on a daily basis.
challenger blew up because of a fuel leak, not the lack ofi an rtos.
For instance right now I'd probably pull up the page for the Intel Core i7 and show them the transistor count.
I say: "You're now in a room. It has <transistor count> light switches. I write the instructions that tell you precisely how to flip those switches. You have <cycle time> to perform each instruction. Also it takes <x> instructions to <do some useful unit of computation>"
It's a bit exaggerated, of course, but it usually shakes their view of computers up a bit :).
In this video, we had a lot of people proudly proclaiming that they didn't have the slightest clue about how the stuff they were regulating works, made terrible and inaccurate apologies, all without bringing in experts who could inform them as to the implication of the law. To add insult to injury, rather than calling them experts, they used derogatory language to put down the very people who knew what they were talking about (lets be clear here, some people use nerd as a badge of honor, but that was clearly not how they were using the word).
I am currently contracted on a project with 1.5 million lines of code and dependencies on hundreds of services written by a number of different teams. It takes a few weeks just to get new developers productive on the code base. How do you even begin to explain the complexity of this to somebody in a way they can really relate to when they barely understand computers?