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. 26.

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

    | |- […] |- images/ |- javascript/ | |- src/ | |- vendor/ Planning
  2. 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
  3. 34.

    @onishiweb • Reasonable length projects • Varying abilities & specialisms

    • Different developers on projects • Various codebases Consistency http://cssguidelin.es/
  4. 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)
  5. 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
  6. 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
  7. 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
  8. 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
  9. 83.
  10. 87.

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

    Justice League? @onishiweb Teams @onishiweb