The issue is that each piece of customized functionality is different. It also changes through time. Much of the functionality is standardized. Many of the plac

The issue is that each piece of customized functionality is different. It also changes through time. Much of the functionality is standardized. Many of the places where customization is expected, hooks are built into frameworks to allow easy extending. Designers come up with new rules that do not fit into the mold that the "automated" tool offers. For example, tool tips that appear only if the ? key is pressed on the keyboard before hovering. Custom code is needed. The customer decides that they don't like the ordering, content, or display of the timezone field. Custom code is needed. The law changes and it in addition to "Male" and "Female", additional values are required for the gender field. Custom code is needed. Country XYZ decides that your software cannot be used as is because the country dropdown contains Fakeystan. Country XYZ considers it part of its territoy. Custom code is needed. There are analogous situations in the real world. However, they are encountered less often as we got used to accepting the standard offerings that are available. True customization is rare. When we build a custom house, most of us decide between one of the handful of standard options that are available on the market. Picking and installing a standard toilet with one of the myriad toilet seats available in the store is easy. But wait until your you get asked to install a plus-sized purple Italian marble bowl with a faux-fur seat that is anti-bacterial, easy to clean, and doubles as a floatation device. These are the problems we are dealing with building software every day.