Adam Onishi - Trophy winning teams
•
0 likes•471 views
“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, large or small needs to ensure that it works together as a cohesive unit in order to produce the best output. In this talk I’ll take a look at how as a development team we can work better together, taking a look at some examples from great sporting teams. Covering everything from coding style guides, team training techniques, and code reviews, all the way through to Dutch Total Football.
Recommended
More Related Content
Similar to Adam Onishi - Trophy winning teams
Similar to Adam Onishi - Trophy winning teams (20)
More from Codemotion
More from Codemotion (20)
Recently uploaded
Recently uploaded (20)
Adam Onishi - Trophy winning teams
- 1. @onishiweb Trophy winning teams Adam Onishi Codemotion Milan - November 2015
- 5. @onishiweb – Jose Mourinho “Players don't win you trophies, teams win trophies.” Teams
- 7. @onishiweb – Jose Mourinho “Players don't win you trophies, teams win trophies.” Teams
- 28. @onishiweb assets/ |- scss/ | |- settings/ | |- tools/ | |- […] |- images/ |- javascript/ | |- src/ | |- vendor/ Planning
- 36. @onishiweb “Code should look as if it's been written by one person, no matter how many people have worked on it” – Mark Otto (@mdo) Consistency
- 38. @onishiweb http://cssguidelin.es/ Consistency • Reasonable length projects • Varying abilities & specialisms • Different developers on projects • Various codebases
- 39. @onishiweb http://cssguidelin.es/ Consistency • Reasonable length projects • Varying abilities & specialisms • Different developers on projects • Various codebases
- 40. @onishiweb • Reasonable length projects • Varying abilities & specialisms • Different developers on projects • Various codebases http://cssguidelin.es/ Consistency
- 44. @onishiweb “Enforce these, or your own, agreed upon guidelines at all times. Small or large, call out what’s incorrect.” – Mark Otto (@mdo) Consistency
- 48. @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
- 49. @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
- 50. @onishiweb Rule 12: The correct number of JavaScript libraries to know is n+1 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. Consistency
- 54. @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
- 95. @onishiweb Share experiences with the team Teamwork
- 100. @onishiweb Teams • Planning • Teamwork • Equality
- 101. @onishiweb Teams • Planning • Teamwork • Equality • Adaptability
- 102. @onishiweb • Planning • Teamwork • Equality • Adaptability • Communication Teams
- 104. @onishiweb Thank you! Adam Onishi Codemotion Milan - November 2015 Attribution-NonCommercial-ShareAlike 4.0 International http://creativecommons.org/licenses/by-nc-sa/4.0/