The statements made in the article do not align with reality - just the idea of what an architect does. After many delivered buildings and many delivered system

The statements made in the article do not align with reality - just the idea of what an architect does. After many delivered buildings and many delivered systems/apps/API's I can say for certain that the analogy just doesn't hold any water. It's probably worse than the 'car engine' mechanic analogy to software. Software is missing a layer of people that role of the Architect provides. They are used more like your lawyer - acting as an advisor and agent on your behalf in your best interest. And allowed to make certain kinds of decisions for you when you are not present (ask to see the contract first!). It just so happens that there is a 'creative' step at the beginning. I wouldn't spec (which is a written doc accompanying the drawings) which brand of steel is used, only the size (W10x44 36ksi). And I don't spec what brand of concrete is used (4" 2500 psi on WWM and #5 rebar on 4" crushed rock on top of a VB, maybe the color and finish if it's fancy). I do spec that it's a brick wall, some steel columns, and the use of bar joists for the membrane roof. I would spec where and how your fire alarms and exit signs are placed due to codes, and I would determine the maximum building volume that could be put on site. And certainly have some details on how to work with seismic-related or energy conservation issues such as the R= value of insulation. But it's up to the General Contractor to submit to the architect during construction - and sometimes provide an 'Alternate bid' during the bidding phase that all of these details get worked out. In other words, after the design is completed but before construction (and finance) has begun. That's when the Software engineer says, 'Hey, let's use Python and Django' to build this - it meets or exceeds all the constraints and fits in the budget.