This content originally appeared on DEV Community and was authored by Keff
What up everyone! ?
2 months ago I became a senior in my company (I don't give a crap), and this got me thinking about what these "roles" and "levels" represent.
- Do they mean anything at all?
- Are they just a reflection of your salary and an ego booster?
- How do they affect junior devs?
- Is it the best way to break down experience levels?
My take
In my humble opinion, these labels just indicate the salary and help inflate the devs ego. While making juniors feel less capable just because a label says so, also making them feel like they all should be seniors at some point (which they don't). If everyone was a senior, the software would be as expensive as Adobe's subscription.
I think there should be some way of separating experience levels, but they should be split and defined better, now they are too broad and nobody knows where the line is.
I've seen "juniors" with 2-3 years of experience be more productive and have a better understanding of the job than some "seniors", that were stuck in the past and did not move forwards (making them obsolete).
What I want to say is, don't give a crap about titles, just do your job right. And don't let titles make you feel better than the rest.
Now, what's your take on this?
This content originally appeared on DEV Community and was authored by Keff
Keff | Sciencx (2021-09-29T08:08:23+00:00) Senior means… ego?. Retrieved from https://www.scien.cx/2021/09/29/senior-means-ego/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.