counterpoint: because it can be patched / updated, client will want it patched / updated. The worse thing on programming, it's hard to estimate a task because i

counterpoint: because it can be patched / updated, client will want it patched / updated. The worse thing on programming, it's hard to estimate a task because it's very dependent on the software architecture. If we're talking about building, you'll know the estimates of adding a sink on a specific room / floor vs adding another floor on the roof. Both need to be reviewed by the blueprints and whether the foundation support another floor if we're talking the later. In software it should be similar, however most of the time management isn't aware of the software architecture and the challenge to make the change. Adding a button to change some value may take either hours to days depending on the architecture, same with adding a sink may take days to months depending on the plumbing blueprint. Which is why in software, sometimes management ask you to add 50 floors to an existing 100 floors building and simultaneously change all the electricity placements on all floors, in under 3 months.