|Sent on:||Friday, April 11, 2014 4:41 PM|
Just skimming over this before shutting down for the night, but this caught my eye:How much does a junior cost out of your velocity?
There appears to be a fear that a junior is very expensive cost to velocity, why, what do they actually cost? I get that context changes everything. But maybe there is something that if we understand here we could reduce the cost for the whole community? For example how would would get familiar with a new codebase fast, what things as a senior do you look up, that you may take for granted.
There’s a potential psychological blocker here to hiring ‘juniors’. It could be that folks know, at the back of their mind, that bringing someone on and getting them up to speed is going to bring home all those shortcuts and tech debt borrowing that you made: that documentation you never wrote, that machine bootstrap script that never got made and setting up your machine will involve a two day process of compiling arcane nginx extensions, none of your specs pass, and that a lot of the codebase is quite terrible. These are the realities for many folks, and some just can’t bare to acknowledge it, which hiring a junior would force them to do.This message was sent by John McDowall ([address removed]) from Vancouver Ruby Meetup Group.
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
To learn more about John McDowall, visit his/her member profile