If it actually meant something we wouldn't have the industry standard interview consisting of seeing if you can do basic comp sci algorithms either. As far as I am aware other engineering disciplines don't get asked to whiteboard something like calculus to see if they can do the basics when they go for a new job
And, yes, the tire fire that is interviewing is a large part of this.
A good portion of the software community does not want a governing body over the industry. If we are going to accept that, then we also need to accept that titles are meaningless because there are no standards.
But, by "muddying", I was referring to the original post I replied to that pimped services for turning people into somewhat-competent web developers and calling them engineers. Sorry for the confusion.
I fully agree, and I think that's a great job to teach to and for people to have. I think conflating it with this-had-better-frigging-work engineering is dangerous to both the profession and the people who trust us to do good work for them (both as employers/clients and as a society).
Engineer means something. Hell, I build systems expecting them to fail and I understand how to proof them, to the best of my time/cost allowances, against failure. I'm still not "an engineer". And--and this is important--I am also not held liable like one.