Currently, I believe Software Architect is a better term/analogy. My dad is an architect that also built his designs: he did it all from design to construction

Currently, I believe Software Architect is a better term/analogy. My dad is an architect that also built his designs: he did it all from design to construction including project/budget management. He's over 70 now, graduated almost 50yrs ago and since then the 'field' has changed: it has become specialized. Now the architect only 'designs' the building, the civil engineer calculates the structure, the PM makes sure times and budgets are met; and there are a dozen more specialists handling a specific task. The same transformation is happening to the production of software to the extent that we now even have UX specialists. Most of us are still like my dad 30 yrs ago, we are 'full-stack' devs, we are craftsmen (or craftswomen!), we do it all. Give it time and the software engineer will have is place with a specific skill and task in hand, the title won't be ambiguous. This is already happening with big ticket projects, it will eventually trickle down to the small ones.