But the original linked article missed why they were not engineers because OP didn't know what an engineer is any more than his coworkers. Its like watching Dn

But the original linked article missed why they were not engineers because OP didn't know what an engineer is any more than his coworkers. Its like watching DnD players who pretend to be wizards while playing the game, argue out of game about why everyone else isn't a real wizard yet getting it all wrong, blaming it on unavailability of components such as ground up unicorn horns, or lack of authority such as a diploma declaring them trained wizards from Hogwarts. They are correct in that they're not really wizards, but they get the reasoning for why they're not wizards wrong. Which is kinda important if the implication is that a lot of software devs want to be wizards, er engineers.