3 ms·
I used to hesitate to call myself a senior dev, but I've come to realise it seems to be used just to refer to someone who can do their job without an excess amo
by kypro 4y ago
I used to hesitate to call myself a senior dev, but I've come to realise it seems to be used just to refer to someone who can do their job without an excess amount of handholding.
Junior devs on the other hand tend to be developers with little to no experience with some of the core technologies used within the role. Typically they'll require some help from more senior devs to get up to speed.
I've been a developer for over 10 years at this point and I'm not really sure I feel like a senior dev. Every week I'm reminded how much I don't know. There's definitely a huge variance in the abilities of senior devs. Some of worked with are been terrible while others have been indispensable to the team. It's always bothered me that variance wasn't reflected in pay or title.
- s__s 4y ago> I've come to realise it seems to be used just to refer to someone who can do their job without an excess amount of handholding. Being competent enough to work independently is an extremely low bar for the distinction of being a senior in your field. In most other industries that just means you’re not a trainee any longer. For example my wife just entered the medical field doing administrative work. She’ll be a trainee for a full year. It will be a decade or more before she’ll be qualified to be in any sort of senior role. I mean at the end of the day I don’t feel that strongly about it, but the problem is that when titles become meaningless it’s very hard to for example, communicate what role you’re hiring for, or who the right person to lead a new project is.