[LegitGandalf]

How do you reconcile how bespoke and ever changing the requirements are for software products vs how stable the requirements are for garages?

I'm asking because I see the construction analogy pop up a lot and I just can't reconcile the two things.

To me the development of a new blueprint for a new kind of garage for a new kind of vehicle operated by a never before seen alien species is a bit closer to creating a software product.

I mean, who would ask a contractor to do what people regularly ask software engineering teams to do?

[thrower123]

Construction isn't a bad analogy. Imagine you're a contractor getting called in to finish a house that some incompetent jabroni started, then got out of their depth and got fired midway. Meanwhile the homeowner has changed their mind and wants an open-concept kitchen, and the building inspector has come back with objections to the wiring plan that need to be rectified.

[LegitGandalf]

The physical dependencies of a house vs the abstract nature of software interdependencies really makes the analogy fail for me. Houses just don't don't regularly fall down 8 times a day because one framer is putting a nail in a new wall and that caused the fireplace to explode.