Trophy Winning Teams - Web Dev Conf 2015

Trophy Winning Teams - Web Dev Conf 2015

“Players don't win you trophies, teams win trophies”. A team works better when they work together, no matter whether the goal is winning the World Cup or creating amazing websites.

Any development team, whether large or small needs to ensure that it works together as a cohesive unit in order to produce the best possible output. This can mean ensuring there's consistency in the code being written. Ensuring everyone stays up-to-date with the fast-moving pace of the web industry. As well as the ability for any project to be worked on by one or more team members at a time and have the ability to be handed over if a developer takes time off.

Fc7368fd45560e1e7401bc80684f5867?s=128

Adam Onishi

October 09, 2015
Tweet

Transcript

  1. @onishiweb Trophy winning teams Adam Onishi Web Dev Conf October

    2015
  2. @onishiweb Sports!

  3. @onishiweb Teams?

  4. @onishiweb Teams?

  5. @onishiweb – Jose Mourinho “Players don't win you trophies, teams

    win trophies.” Teams
  6. @onishiweb My teams…

  7. @onishiweb dxw Teams @onishiweb

  8. @onishiweb Great Sporting teams

  9. @onishiweb Planning Sports

  10. @onishiweb The “play” Sports

  11. @onishiweb Sports @onishiweb

  12. @onishiweb Teamwork Sports

  13. @onishiweb Maul! @onishiweb

  14. @onishiweb Everyone is equal Sports

  15. @onishiweb Sports @onishiweb

  16. @onishiweb Adaptability Sports

  17. @onishiweb Sports @onishiweb

  18. @onishiweb Communication Sports

  19. @onishiweb Sports @onishiweb

  20. @onishiweb @onishiweb Sports

  21. @onishiweb Great teams Sports

  22. @onishiweb Sports @onishiweb

  23. @onishiweb Baseline

  24. @onishiweb Boilerplate Planning

  25. @onishiweb https://github.com/wearearchitect/Frontend-Boilerplate Planning

  26. @onishiweb assets/ |- scss/ | |- settings/ | |- tools/

    | |- […] |- images/ |- javascript/ | |- src/ | |- vendor/ Planning
  27. @onishiweb Gulp! Planning

  28. @onishiweb Pattern library Planning

  29. @onishiweb Planning @onishiweb

  30. @onishiweb https://github.com/madebymany/css-patterns Planning

  31. @onishiweb Coding Consistently

  32. @onishiweb – Mark Otto (@mdo) “Code should look as if

    it's been written by one person, no matter how many people have worked on it” Consistency
  33. @onishiweb Consistency

  34. @onishiweb • Reasonable length projects • Varying abilities & specialisms

    • Different developers on projects • Various codebases Consistency http://cssguidelin.es/
  35. @onishiweb http://codeguide.co/ Consistency

  36. @onishiweb http://sass-guidelin.es/ Consistency

  37. @onishiweb https://github.com/onishiweb/code-style Consistency

  38. @onishiweb “Enforce these, or your own, agreed upon guidelines at

    all times. Small or large, call out what's incorrect.” Consistency – Mark Otto (@mdo)
  39. @onishiweb Consistency @onishiweb

  40. @onishiweb @onishiweb Consistency

  41. @onishiweb The Rules https://github.com/wearearchitect/Frontend-Rules Consistency

  42. @onishiweb Where possible all of these rules should be followed

    to the letter. But, all rules are open to discussion and review. Obviously there are also times where a rule must be broken, but you should be able to explain why it was necessary and what benefit it gave you. Rule 1: Obey the rules Consistency
  43. @onishiweb Rule 4: It's all about the bike code. None

    of these rules are personal, there is no agenda in the rules; it's all about the code. The rules are here to help us write good code and work together as a team. It's about learning as well, front end development is continually evolving with new techniques and new tools becoming available all the time, the rules will keep evolving with these best practices and be updated over time. Consistency
  44. @onishiweb Most front end developers are familiar with JavaScript and

    jQuery, but there are now more frameworks than you can shake a stick at! Whether it's Angular, Meteor, Backbone, Ember, Coffeescript, or Node.js there's always something new to learn. Rule 12: The correct number of JavaScript libraries to know is n+1 Consistency
  45. @onishiweb Consistency

  46. @onishiweb Consistency @onishiweb

  47. @onishiweb ”The Rules” Consistency

  48. @onishiweb • Be consistent. • Don't rewrite existing code to

    follow this guide. • Don't violate a guideline without a good reason. • A reason is good when you can convince a teammate. https://playbook.thoughtbot.com/#style-guide Thoughtbot’s Playbook Consistency
  49. @onishiweb Enforcing Consistency

  50. @onishiweb Linting Consistency

  51. @onishiweb Code reviews Consistency

  52. @onishiweb Consistency @onishiweb

  53. @onishiweb C0de reviews Consistency

  54. @onishiweb Reading good code https://www.youtube.com/watch?v=mW_xKGUKLpk Consistency

  55. @onishiweb Pull Requests Consistency

  56. @onishiweb Consistency

  57. @onishiweb Consistency

  58. @onishiweb Nothing Personal Consistency

  59. @onishiweb Consistency @onishiweb

  60. @onishiweb Code review etiquette Consistency

  61. @onishiweb Keeping consistency Consistency

  62. @onishiweb Documentation

  63. @onishiweb General Documentation

  64. @onishiweb Contextual Documentation

  65. @onishiweb For Reference Documentation

  66. @onishiweb Onboarding Documentation

  67. @onishiweb Documentation @onishiweb

  68. @onishiweb Onboarding Documentation

  69. @onishiweb Documentation @onishiweb

  70. @onishiweb Teamwork

  71. @onishiweb Smaller teams Teamwork

  72. @onishiweb Mentorship Teamwork

  73. @onishiweb Responsibility Teamwork

  74. @onishiweb Buddy System Teamwork

  75. @onishiweb Learning Teamwork

  76. @onishiweb Sharing knowledge Teamwork

  77. @onishiweb Developer déjeuner Teamwork

  78. @onishiweb Group code reviews Teamwork

  79. @onishiweb Teamwork @onishiweb

  80. @onishiweb Conferences & Meet ups Teamwork

  81. @onishiweb Share the experiences with the team Teamwork

  82. @onishiweb Development teams

  83. @onishiweb The Architect dev team, my team! Or funny gif!

    Justice League? Teams @onishiweb
  84. @onishiweb Tools specialist Teams

  85. @onishiweb Lightning- fast coder Teams

  86. @onishiweb … Teams

  87. @onishiweb The Architect dev team, my team! Or funny gif!

    Justice League? @onishiweb Teams @onishiweb
  88. @onishiweb Great dev teams Teams

  89. @onishiweb • Planning • Teamwork • Equality • Adaptability •

    Communication Teams
  90. @onishiweb Teams @onishiweb

  91. @onishiweb Thank you Adam Onishi Web Dev Conf October 2015