|Sent on:||Tuesday, April 15, 2014 1:11 PM|
From: Eric Brooke <[address removed]>
Date: Apr 15,[masked]:44 AM
Subject: [ruby-112] From a business perspective is it a good idea to build in Rails?
To: [address removed]
Do you have the developers you need onboard? Is what I ask, now.
There are some companies in Vancouver who have being trying to find senior developers for the last six months without any luck. I know four companies in Vancouver who have over 10 rails developers who want to double their number by years end. Then there is a bunch of startups (you know under 10 people) who are desperately trying to get, that one extra developer.Several recruiters, I spoke to said to me they cannot believe the approach that some companies in Vancouver,BC are taking, waiting for that perfect Unicorn, when in time it is taking them to recruit they could have grown a Junior to an Intermediate. Whilst in other markets such as Toronto, Seattle, Portland, Boston, New York and San Francisco. Companies are looking for the right people to grow.And that is before you talk about pay.There is one shining example and that is Clio, who look at all at the full range, had a great chat with one of their seniors, who showed me the offices, which frankly is the best environment I have seen so far, their mobility between projects is high, as is their tolerance for learning new languages i.e. Objective C. Their tech testing is fair, no rails question but a good set nonetheless.The simple fact is if we do not grow more rails/ruby developers the framework/language may c hange to fit the needs of the businesses that want to build their web/mobile applications now and not wait six months to find someone. Six months could kill some businesses.Here is my current hypothesis for whether a company will employ juniors:
- The more Seniors in a company the bigger the reluctance to coaching juniors.
- Where Seniors are not comfortable with collaboration, and human interaction. Sometimes they believe they are great at humans (or really do not care), where as they come off as just arrogant.
- Where there is a mix of Intermediates and Seniors there is an openness to coaching juniors.
- Intermediates who are generally more open to coaching, they seem to follow up their words with actions..
- Where the organization culture is a true mix of learning/reflection/growth/mobility.
- Survival mode companies, do not employ juniors, where the priority is velocity
- Where the culture is very competitive and “male”, do not employ juniors, unless you are a math graduate..
- Where the priority is on culture not just velocity, do. Sometime driven by business not technology people.
- Where there is the wider coverage of tests, then there is less reluctance to bringing on juniors.
- Where the code climate GPA is higher then 3
- Where the Seniors have had multiple jobs in the past they tend to be more open.
- Where the Seniors have worked both small and large companies
- Confident, open Senior who just thinks it is the right thing to do, because they see coaching as part of their growth and have stepped over the fear. And the business has not oppressed them into survival mode.
- Where the technologist actual bought into community, and not a means to an end i.e. their pay.
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Eric Brooke ([address removed]) from Vancouver Ruby Meetup Group.
To learn more about Eric Brooke, visit his/her member profile
To report this message or block the sender, please click here
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages
Me etup, POB 4668 #37895 NY NY USA 10163 | [address removed]