That's a good comparison, but I'm stuck on the "now".
Why exactly do you think code wasn't clay until a few years ago, and why is it now? It's a bit hard to tell from the article where exactly you draw the line between the two stages.
For example, the more experience I gain, the more annoyed I get when software or code is compared to machines, cars, or factories. These days, I exclusively use cooking as an analogy because it shares so many traits with software development. Using the same ingredients at the same time doesn't necessarily produce the exact same result. Everyone does things slightly differently, and there's a whole spectrum of outcomes, from factory-produced frozen pizzas to five-star Michelin dishes.
That's why I use this analogy whenever we discuss architecture and similar topics. I feel like it gets my point across much better.
Why exactly do you think code wasn't clay until a few years ago, and why is it now? It's a bit hard to tell from the article where exactly you draw the line between the two stages.
For example, the more experience I gain, the more annoyed I get when software or code is compared to machines, cars, or factories. These days, I exclusively use cooking as an analogy because it shares so many traits with software development. Using the same ingredients at the same time doesn't necessarily produce the exact same result. Everyone does things slightly differently, and there's a whole spectrum of outcomes, from factory-produced frozen pizzas to five-star Michelin dishes.
That's why I use this analogy whenever we discuss architecture and similar topics. I feel like it gets my point across much better.