Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
This seems to be quite common. I started more than 4 years ago my professional career and so far, i did not have 1 senior who teached me in 2 different jobs.
My first 'senior' in my first job took anywhere between 2-5 days to answer a question (heck, there were pull requests that were not reviewed for 9 months. She did got fired for other reasons)
The second job, the "senior" developer has no experience in frontend development and i've been hired as frontend dev. -
@BordedDev I'll probably go even further than that and make them do something together.(even then, the former junior is right next to my desk and gets to see everything I do to the new junior). I just need a few days to test the waters, I just don't have any clear idea right now because the situation developed quickly, but tbh I'd be a fool not to make the former junior play some sort of part. He's young... but he's equally talented and hard working; probably even more than I was at that point in my career. I just need to iron out the details a little bit.
-
UPDATE: as per my own arbitrary decision, every junior is hereby entitled to two whipping sessions every day, at 11am and 4pm. These whipping sessions will have precedence over any other task I have control of.
During these whipping sessions -which might last anywhere between 5s and 50m depending on how stuck they are in the mud- they'll be provided with programming patterns, good practices, fixes for the most obnoxious bugs they are encountering, tips to figure out on their own what should fall within their domain and verbal diarrhea.
Let's go. -
-
@IHateForALiving a firm slap to the back of the head for not problem-solving ;P
-
@BordedDev he's a junior frontend developer and the dockers were entangled beyond recognition; so much so, even I needed the help of a senior devops and 3h to untangle the mess. He gets a pass; the tech lead which was supposed to help him for the previous year, of course, should and will be fed to a wood chipper.
-
@IHateForALiving oh god how do you entangle dockers?
-
@IHateForALiving That's good to know, I had one who had issues with just running `docker compose up`... (turned out to be storage issues afaik, and IMO the job should have bought him more storage)
-
@Lensflare our env variables, networks and docker commands were borked beyond belief for a while now, nobody ever cared to check (they're probably going with the same dockers running for months, never restarting it).
I realized it and fixed it two months ago, but I did so in my own branch (not yet merged in develop) and ofc the junior was unaware of all this; on top of that, his environment had some further problems with missing env variables and the likes.
The junior dev I've been unofficially mentoring for the past 6 months has now been assigned to me officially. On top of that, I got myself a second junior everybody neglected and was tasked to whip him in shape.
Next step is going to make a developer out of this fucker or die trying. And then I'm going to call several tech leads a cunt for hiring a junior dev and letting that person down for months.
Every junior deserves a stern, dedicated mentor, a thick affectionate whip on their back to correct their juniorly mistakes and all the support they deserve to grow into the merciless professionals you need to handle complex features beyond recoloring a button.
If you, as a tech lead, are unwilling to teach a junior, you shouldn't take the position of a tech lead, nor the salary.
rant
junior dev
tech lead