How to grow a perl team
?Download as PPTX, PDF?
1 like?1,936 views
Good developers cannot be bought at the meat market. Especially not good Perl developers. Observation of teams over several decades as a developer, a manager, an academic and industry trainer, have crystallised into five core principles to make growing a team healthy and productive.
How to grow a perl team
- 1. tweet: @geekuni Andrew Solomon andrew@geekuni.com # HOWTO Grow a #!perl team
- 2. tweet: @geekuni my $self = shift;
- 7. tweet: @geekuni The Challenge - Team Growth
- 8. tweet: @geekuni Model 1: 13% Growth, No churn Developers never die
- 9. tweet: @geekuni Model 2: 13% Growth, High Churn Stick around for 2 years
- 10. tweet: @geekuni Model 3: 13% Growth, Moderate Churn Stick around for 5 years
- 11. tweet: @geekuni HOWTO grow a Perl team with Moderate Churn
- 12. tweet: @geekuni 5 mod-churn principles Ownership Passion Balanced Recruitment Continuous Learning Communication
- 16. tweet: @geekuni 2. Continuous Learning
Editor's Notes
- Research and Teaching Manager: Team + budget + deadlines
- online retail, online search engine, advertising… Training People and companies in Perl online
- Blue line is the goal for growth The ideal way - your developers never leave
- The bad way your developers leave on average after 2 years. recruitment rate is hypothetical - there aren’t enough Perl developers out there
- Early Stage good communication skills experienced and courageous guesswork and prediction out the door quickly
- Mature good communication skills some experts but not all. hard to find, easily get bored some beginners who can stick around for career progress. Easy to learn - Perl. Slow to learn - the business
- Very few people learn Perl at uni. Hard to teach. If it’s a good job, good developers to learn what they need to know - and find it interesting Time for Training In house training (like Geekuni) to get people up to speed with the Essentials and don’t get left behind With this momentum, further self training with hack day projects Set aside hack days set aside time to pick them up to turn them into projects when they have potential business value
- Very few people learn Perl at uni. Hard to teach. If it’s a good job, good developers to learn what they need to know - and find it interesting Time for Training In house training (like Geekuni) to get people up to speed with the Essentials and don’t get left behind With this momentum, further self training with hack day projects Set aside hack days set aside time to pick them up to turn them into projects when they have potential business value
- DON’T send them off on their own with One liner project spec. That’s outsourcing. ensure understanding of the business goal - work as a team of developers and stakeholders encourage developers to question the specs to keep clarifying the end goal and scope. encourage collaboration - presentations, code reviews, pair programming, shared ownership Result: Happier developers Healthy work dynamic More productive
- Shares are good but project ownership/responsibility is better Developer should be part of the entire lifecycle. requirements gathering design acceptance testing release bugs/features maintenance
- Shares are good but project ownership/responsibility is better Developer should be part of the entire lifecycle. requirements gathering design acceptance testing release bugs/features maintenance
- Developers are artists are passionate want their creations out there - e.g. CPAN, public site, academic paper want to belong to the community Support these things and they’ll stick around
- Developers are artists are passionate want their creations out there - e.g. CPAN, public site, academic paper want to belong to the community Support these things and they’ll stick around