O slideshow foi denunciado.

Legis pactum building high performance teams

17 visualizações

Publicada em

A talk on building high-performance teams on #farodevday

Publicada em: Tecnologia
  • Seja o primeiro a comentar

  • Seja a primeira pessoa a gostar disto

Legis pactum building high performance teams

  1. 1. Building High Performance Teams
  2. 2. who am I ? By passion: Developer/Architect By title: CEO & CTO By Nature: Curious In reality: Company Handyman Linkedin: miguelp Twitter: lookatitude (company twitter) Email: miguel.pinto@lookatitude.com
  3. 3. Building High Performance Teams Building Teams
  4. 4. Where do you start? Recruiting Onboarding Retention
  5. 5. What are you looking for? - Recruiting A. Define the profile B. Look for the right candidate C. Define expectations in a realistic way D. Sign the contract.
  6. 6. Getting started - Onboarding ● How long does it take to setup the environment? ● Are there standards? ● Are there workflows in place?
  7. 7. Common problems - Onboarding ● Inconsistent set up environments ● Not measuring — or managing — code complexity ● Forgetting code design ● No style guide ● Too many comments, or no comments at all ● Too much documentation or no documentation at all ● Working with monoliths
  8. 8. Maintaining the team - Retention ● Competitive compensation. ● Good space ● Good moral ● Free stuff (coffee, water, sodas) ● Team events/activities
  9. 9. Common problems - Retention ● Inconsistent promotions ● Recognition is close to none ● Gradual loss of motivation ● Consistently failing to meet team’s expectations
  10. 10. Onboarding - High performance Create pre-set up environments, that run on any platform. Create documentation for the setup (list of software/tools requirements, pre setup credentials and so on). Start with small but quick tasks that can be done in 1 day. GOAL: Average time for 1st commit, 1 day or less
  11. 11. Retention - High performance Measure all things Leverage the data you have
  12. 12. Example 1 - Performance gains
  13. 13. Example 1 - Performance gains
  14. 14. Example 1 - Performance gains
  15. 15. Example 1 - Performance gains Before After
  16. 16. Example 1 - High performance ● Improved readability ● Reduced the amount of to be understood ● Clear code requires less documentation ● Easier to spot and fix bugs ● Reduces duplication and code complexity
  17. 17. Retention - High performance Back to the basics Improve foundations
  18. 18. Back to the basics - High performance Problem: Get all products from the database and their related categories
  19. 19. Back to the basics - High performance Background: Given that the database has only 2 products with 2 categories each.
  20. 20. Back to the basics - High performance Question: How would you get the result writing only 1 query?
  21. 21. Back to the basics - High performance Question: How would you get the result writing only 1 query? Using a join
  22. 22. Back to the basics - High performance Follow up question: Ok, so how many operations are you executing?
  23. 23. Back to the basics - High performance Other questions: What is inheritance? What problem does it solve? When should it be used? Why should it be used? Pros and cons of that approach?
  24. 24. Back to the basics - High performance - Re-Learn the basics - Understand the context - Teach them to your teams - Understand why - Uncover pros and cons
  25. 25. Experiment - High performance - Try different approaches to the same problem - Try the new things on the block (understand their design and what advantages did they got from it) - Present your findings in workshops/trainings, meetings. - Organize your code repositories - Create and share documentation BE CONSISTENT
  26. 26. Conclusion - High performance - Create procedures - Define your coding styles - Decide on the architecture - Explain why, continuously train your team - Treat your peers as humans BE CONSISTENT
  27. 27. Miguel Pinto Email: miguel.pinto@lookatitude.com Url: http://www.lookatitude.com Q&A

×