Ranter
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
Comments
-
Sounds like the training role might not be the right one for you. If your patience is strained as much as this post suggests and your students are struggling to learn the ropes of your setup or organisation, perhaps it would benefit everyone if you transferred responsibility.
-
Pelle1308yThey are actually junior devs, so, they can't know anything if they were not taught so.
-
@CrankyOldDev our training approach is simple. We firstly let them watch excellent training videos from Lynda then we do a few labs on a weekly basis. We had given them a group project that was meant to expose them to the inner workings of git, Xcode and swift. They performed fairly well for beginners. We highlighted this in our weekly review in addition to the problems such as adherence to human interface guidelines and also the fact that they should work on one repo not multiple repos. As we team we agreed on a do-over project, wherein they would try to address the shortcomings of the previous project. I had also highlighted the need for them to check in with me before they attempted to do new things that they are unsure of, this request has mostly gone unused. They have been fighting the guidelines from the word go and resorted to their own informal ways of doing things.
Related Rants
I've been training a few junior devs for about a month in the use git and adopting to a collaborative team workflow. My blood is boiling at this point. As part of the training we had the junior team build an iOS app. Their solution was for each of the to have a git repo of their own and a master repo for everyone. If they can get it to work in their individual repos, they would move that code over to the master repo. This seemed to have worked for them but it's completely wrong in trying to understand how integrating their work by the hour or so would benefit everyone involved and ultimately how that can influence the quality of the product. So I highlighted the problem with the individual repos and encouraged the use of a single remote repo. OOP is none existent all the code is slapped into a view controller. I have about given up. Let's see what this week will bring.
undefined
dev
git
workflow
failure