Do we really need to waste time on those namings? It's just a name, if I'm getting paid enough and it doesn't limit me in my day-to-day work, then I'm fine getting called junior my whole life, even with 10 years of professional experience. Some of people pay attention to that, but that's just naming. Some of the companies compensate bad salary/atmosphere/projects with titles, which in the end are just about prefixing your title with a single word on LinkedIn. Is it really worth it?
I don't really like that, that's why I would be happy to call everyone developers or software engineers etc. It simply fixes a problem with correct naming and finding out, who is senior developer, which in the end doesn't really matter, because everyone has his own definition (as you can see in discussion here).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Do we really need to waste time on those namings? It's just a name, if I'm getting paid enough and it doesn't limit me in my day-to-day work, then I'm fine getting called junior my whole life, even with 10 years of professional experience. Some of people pay attention to that, but that's just naming. Some of the companies compensate bad salary/atmosphere/projects with titles, which in the end are just about prefixing your title with a single word on LinkedIn. Is it really worth it?
I don't really like that, that's why I would be happy to call everyone developers or software engineers etc. It simply fixes a problem with correct naming and finding out, who is senior developer, which in the end doesn't really matter, because everyone has his own definition (as you can see in discussion here).