As sibling comment implies, constructing things physically can often have the "forever needing to be built upon" aspect just like software. The difference that

As sibling comment implies, constructing things physically can often have the "forever needing to be built upon" aspect just like software. The difference that you are probably feeling here, at least from what i can see, is that once a house is built by a construction company, it is "handed over" pretty much completely, whereas with software there is almost never such a handover, but instead a "support period". This I suppose can lead to fatigue as you end up never reaching a "final final" product per se like the house. Personally, i have always found it helpful to plan by milestones/major versions, such that it, in a "hack the human brain" kind of way, provides a synthetic almost-copy of that " ah, all done, time to move on" that the human brain gets when a house is built, or a mountain is climbed. Interesting philosophies hidden within all this, particularly for team leads and such of dev teams.