The job titles seem to say more about the people hiring than about the jobs themselves. I have often thought that making software has at least as much in commo

The job titles seem to say more about the people hiring than about the jobs themselves. I have often thought that making software has at least as much in common with cooking or sewing as it does with engineering or architecture, as in "software architect" or "software engineer"- yet there are no software chefs or software tailors. Perhaps executives are uncomfortable knowing less about a fundamental aspect of their business than a chef or a tailor but if an engineer or architect knows something they don't, well, those are demanding disciplines that the executive can be forgiven not having mastered. Likewise there are no attire engineers or food architects because we might be more reluctant to have our waistline measured by an engineer or to tell an architect in fine detail how our meal should be prepared. It also occurs to me that both architecture and engineering are traditionally male-dominated fields. On the other hand, "computing" was originally considered woman's work[0]. Whatever title I propose is ultimately moot if the people hiring would rather call their employees software architect, software engineer, software lumberjack, etc. However, since you asked me, I think "codewright" has a ring to it.[1] [0] https://en.wikipedia.org/wiki/Computer_(occupation)#Wartime_computing_and_electronics https://en.wikipedia.org/wiki/Computer_(occupation)#Wartime_... [1] https://www.thefreedictionary.com/Wright https://www.thefreedictionary.com/Wright