There, made it an even thousand claps. :D

One detail I think you're missing is that titles are... well.. mostly bullshit. Bullshit in two flavors.

1) Something a programmer gives themselves to brag to their friends about.

2) Something bosses give -- typically alongside more work -- instead of a pay raise commensurate to the job or experience level of the worker.

I've really soured on the endless stream of nonsense we're seeing in job titles... though that started back in the mid '90's when i was a "regional Vice President of IT" for a major national insurance company.

Turned out they handed out vice presidencies the way a predator hands out candy to children from a white panel van.

The building I worked in -- one of three dozen across the nation -- half the bloody staff were "vice presidents". It was ridiculous.

I feel the same way when people call themselves "software architect" or "engineer"... particularly when they seem utterly devoid of knowing the basics of usability, accessibility, specifications, guidelines, or any of the other ACTUAL engineering concepts that define design. Admittedly this is far worse on the front end with artists under the DELUSION they are "designers".

Equally at fault in my mind is the "Peter Principle" where invariably in companies people get promoted one step above their skill level. It's why a lot of times middle-management turns into an epic failure.

But seriously I've lost count the number of times this past year someone said they were a architect, or engineer, and all I can think is "bullshit, you're a programmer; get over yourself!"

Though it's also troubling when people with such lofty titles and loftier aspirations I wouldn't trust to code their way out of a piss soaked paper bag with a hole in the bottom. See "Framework stupid"