8
dittrx
17d

In recent years there has been a massive shift in dev positions and their responsibilities. At least in all the companies, I've worked with.

Interns are now treated like Juniors.
Juniors are now treated like Mids.
Mids are now treated like Seniors.
Seniors are now treated like Architects.

I think some devs(now seniors) forgot how much easier it was to get into this field years ago and how little they had to know to start.

Sad reality.

Comments
  • 4
    I think that's every field as time goes on, things change and different tasks get spread out among various roles.

    Partly because:

    People become used to the tasks given and realize more can be delegated down / there are new tasks that seem bigger.

    Also because everyone is full of shit about how super awesome they are and they did X, Y, Z and everyone 'seems' more qualified than they are ;)

    Straight up BS 'job requirements' inflation

    And lots of other reasons.

    Back in the .com days, decades ago I was a shitty ass community college 'student' who did PC support over the phone, I applied for a job after a buddy got a job after graduation. I applied even if only to just 'get experience interviewing'.

    I got stupid lucky (by no means was this something you could just 'do' the), I got a good paying job and my foot in the door in the tech industry because I demonstrated I could 'troubleshoot'.

    The requirement on that job is now a masters degree (for no fucking reason).
  • 6
    I think it's more to do with the fact no-one can agree on what any of these terms mean in the first place, and everyone's accepted they're way more fluid now than they were. In particular, the days of a high level "architect" telling you exactly how to structure your code, and a junior to mid doing the grunt work of then writing it are long gone (fortunately.)

    I've always ignored these terms near entirely, and instead made a point of asking about responsibilities in interview. I've no interest in being a "senior" in title, but being told what to do in practice and just being a "monkey see monkey code". On the flip side, I don't care if I'm a mid on paper, but managing my own team & product. Some people are fussed by that, I couldn't give too hoots. Call me "almighty overlord of the bytes" for all I care.

    Personally, intern aside, I'd be in favour of removing these terms entirely. They're misleading, inconsistent, and practically useless.
  • 1
    So in other words, devs are now better than before. How is that a negative?
  • 2
    I actually have more of an issue with the idea that all developers are now also product owners / project management experts.

    I'm not great at planning out features, or diplomatic communication with stakeholders.

    Or things like QA, devops, legal, etc get shoveled onto devs. I mean sure I know about most AWS services, set up a DB cluster or configure kubernetes — but that's for my own curiosity & fun. If you need that shit to be managed for production, hire a devops specialist.
Add Comment