Team Communication Through Code

Team Communication Through Code

297d4a4b165eb79b7e341645a05c70d6?s=128

Rachel Ober

September 13, 2014
Tweet

Transcript

  1. 2.
  2. 4.

    4 • Verbally • Facial expressions & body cues •

    Written language • Experiential learning • …and more How do people communicate with each other every day?
  3. 6.

    Rachel Ober Sr. Front End Developer • Started August 2012

    • Lives in Brooklyn • Plays Pokémon • Owns a Corgi 6
  4. 7.

    7 • A case study in how a small start-up

    transitions through growing stages • Techniques for dealing with interdisciplinary teams • New ways to think about collaborating with your teammates • Documenting your knowledge in different, but easily distributed formats Key take-aways
  5. 8.
  6. 10.
  7. 12.
  8. 13.

    13

  9. 14.

    14

  10. 15.

    15

  11. 18.
  12. 19.
  13. 20.

    20

  14. 21.
  15. 22.

    22 • Solve problems • Work independently • Have idea

    they want to work on • Make money • Creative outlet • etc. Why do (I think) people get into development?
  16. 23.
  17. 24.
  18. 25.
  19. 28.
  20. 29.

    29

  21. 30.
  22. 32.
  23. 33.

    33 • Front End developers pair with a Designer 2x/week

    • Designer communicates designs • Front Ender mocks up possibilities with Designer Execution
  24. 34.

    34 • Designers have deeper insight into development • Developers

    understand the Designer’s intention • Can quickly determine if something is going to “work” or not Effects
  25. 36.

    36 • It doesn’t always make sense to pair all

    the time • Dedicated Designer and Front Ender on each feature team who collaborate • Grab the right people and work in a conference room How it’s changed
  26. 37.

    37 • Before meeting, pick the topic you are going

    to explore • Sometimes a session can be exploratory, sometimes set an expectation of what you want to accomplish • Set time limit • Come prepared • This can be applied to any type of pairing session (Developer/ Developer, Designer/Developer, Designer/Designer) Tips & tricks
  27. 38.

    38 • Take breaks • Discuss the meaning behind the

    design so that the developer understands • Discuss technical limitations to a possible design • Show how things change in the browser in real-time • Grab a conference room • Mix disciplines! (UX/Design/Developer) Tips & tricks
  28. 41.

    41 • How files should be set up • TABS

    or SPACES • Best practices • Variables naming • …and more Code styles guides
  29. 42.

    42 • Code review can concentrate on more architecture changes

    • A contract that developers make • Write in a way that everyone should be able to understand Why a coding style guide?
  30. 43.

    43 • Take a look at other companies’ coding style

    guides • Work with your team members to determine what your own best practices are • Write it down in your company’s intranet or in a Gist file on GitHub • What you do code reviews point to the style guide first if the developer should take care of those low hanging fruit first Execution
  31. 44.
  32. 45.

    45 “Remember to use color variables…” Side effects “Alphabetical order

    please!” “We have a mixin for that…” “Can you name this better?”
  33. 46.

    46

  34. 50.
  35. 51.
  36. 52.
  37. 55.
  38. 56.

    56 • Holistic design • Individual teams but ownership of

    key features • Come up with a system that works for your team • Communicate this system to other teams so they can use it too! Solution
  39. 60.
  40. 61.

    61 • Accessible to anyone in the company • Made

    up of visual, usable components • Neatly organized • Includes code and documentation on how to use it • Includes Designer notes and considerations • An example of what appears on the site A good pattern guide is…
  41. 62.
  42. 63.
  43. 64.
  44. 66.
  45. 69.
  46. 71.

    71 • Know what they don’t know • Wants to

    make themselves better • Listen to what the job entails and gets excited • Want to learn from others Interesting interviewees
  47. 75.

    75 • Pair with someone • Mentor a new employee

    who is within your discipline • Offer small tweaks to your development cycle • Get Excited!!!! Small changes
  48. 76.