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
-
Ok, but 3 years of experience doesn't mean much nor does a degree.
A degree shows that you have the inclination to stick out the world of academia.
Three years of experience is a long time but not in comparison to say 20. I've worked as a windows developer for 18 years but the first 10 were finding my feet. -
@philcr part of why I posted this was to see if my expectations are unrealistic. I've got 17 years of web development experience, and yeah, the first 10 (give or take) were... embarrassing in retrospect. True, I didn't have the (dubious) benefit of a degree, but I had my share of sloppy copy-pasta.
So I appreciate you bringing some perspective to this. I'm frustrated with my job in general, and I'm really trying not to be too harsh on the guy (which is hard, because I literally have to spend more time checking his work and holding his hand than I get to spend on actual coding). -
@beofett it might be useful not to shield the gent from the consequences of his actions. Pain is a very useful teacher sometimes. If he has to fix something that came about because of his ill thought out choices, future decisions maybe better.
In a way junior dev is subjugating you by folding you into his flawed dev process. -
@kunashe I don't fix his stuff for him. I just point it out and make him fix it.
Unfortunately, the familiar scenario is that I give him fairly specific guidelines on how to architect the code assigned to him (e.g. "create these three components, which need to provide the functionality described in these user stories and wire frames") , which results in either detailed explanations every 2-3 hours of every problem, solution, and success he encountered so far, or "I couldn't figure out how to do it the way you said, so instead I did {insert unworkable solution}".
While logging a boatload of bugs on the code my junior dev checked in, I added a couple of items to our product backlog.
Instead of fixing his bugs, junior dev started pulling things from the backlog. I found this out when he messaged me about the requested search results sorting.
His message was:
"hey, the sorting is going to be harder than I thought. Angular 2 dropped native support of filters. But I did find an MIT licensed npm package that should let me add sorting functionality to our JSON data objects. "
Um... You know you can sort using plain JavaScript, right?
BTW, junior dev has more than 3 years of professional experience in addition to a degree.
undefined