I see those terms as useful, but not based on years of experience or number of libraries/frameworks. Instead, it's a way to describe the mental and technical maturity that a developer displays, not only with regard to code quality in the simple sense but also but also in relation to making sensible and maintain decisions from a larger architectural and business perspective.
That of course doesn't mean that everyone uses it in that sense, or that some people use words to trick or deceive (like fullstack = we'll need you to do everything, at an unreasonable pace).
"it's a way to describe the mental and technical maturity a developer displays" - this is what terms such as junior, intermediate, and senior mean to me and also a number of companies which I have worked for.
My current employer also rates non-tech skills, such as sensible decision making, self direction, client interaction etc, when considering the seniority of staff and for performance reviews.
I really like your consideration of this. This is so hard to quantify and makes up such a huge part of the criteria of being considered an experienced developer by others.
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.
I see those terms as useful, but not based on years of experience or number of libraries/frameworks. Instead, it's a way to describe the mental and technical maturity that a developer displays, not only with regard to code quality in the simple sense but also but also in relation to making sensible and maintain decisions from a larger architectural and business perspective.
That of course doesn't mean that everyone uses it in that sense, or that some people use words to trick or deceive (like fullstack = we'll need you to do everything, at an unreasonable pace).
"it's a way to describe the mental and technical maturity a developer displays" - this is what terms such as junior, intermediate, and senior mean to me and also a number of companies which I have worked for.
My current employer also rates non-tech skills, such as sensible decision making, self direction, client interaction etc, when considering the seniority of staff and for performance reviews.
larger architectural and business perspectiveI really like your consideration of this. This is so hard to quantify and makes up such a huge part of the criteria of being considered an experienced developer by others.