The person who cooks and serves you a hotdog at an airport concession stand and Michelin star chef have the same job but they aren't hired to do each other's work.
Being familiar with people in the food industry, I think they'd find it pretty offensive to call someone in the role of a "cook" the same as calling someone a "chef". They have very different meanings.
That does seem like a distinction that the software industry needs to work out. The software developer differences between a cook, a sous chef, and a chef, or Nurse versus an RN versus a Doctor, or a Dental Hygienist versus a DMD, or a paralegal versus a Lawyer.
Isn't that the distinction between "Programmer" and "Architect" that some places use? Although, it isn't really standardized.
Not to me. I think the distinction between these titles are silly. Part of programming is architecting applications. There really isn't a way out of it unless you've just been maintaining and patching up existing code your entire life.
I'm not settled. Do you see a difference between designing and implementing? From experience, I do... but I'll happily hear other opinions.
The line seems blurred. I've found the end result is much more desirable designing and iterating on existing code as you implement.
I didn't call anyone a cook. I mention someone who cooks. Chefs cook too (if they are any good).
Sure. But I think capital 'C' Chefs would argue that they don't just cook. I think there's something of a semantic difference.
Do we really need to start taking offense to this sort of thing? Does it improve the world in any way? Remember offense is something that you choose to take.