How design happens at GitHub (ScotlandJS, 2014)

Transcript

1. HOW DESIGN HAPPENS AT GITHUB ! cobyism — ScotlandJS 2014

2. @cobyism

3. None
4. None
5. None
6. None

7. DESIGN it happens

8. None
9. None

10. Pull Requests help settle arguments.

11. Pull Requests keep you grounded in reality.

12. Design happens in ...

13. Design here is real.

14. Design it once, not twice

15. Design here is always current.

16. Just commit.

17. big
 picture Focus on the first

18. Design happens with prototyping.

19. [ REDACTED ]

20. Design happens with lorem ipsum
 dolor sit amet.

21. Design happens with real data.

22. None

23. Design happens hidden behind feature flags.

24. def new_feature_enabled? … end

25. def new_feature_enabled? preview_features? end

26. def new_feature_enabled? preview_features? && team_access?(:some_team) end

27. None

28. def new_feature_enabled? true end

29. Beware of
 feature flags.

30. Dogfooding is powerful, but it has it’s limits.

31. Design happens with feedback.

32. Design happens with quantitative feedback.

33. Design happens with qualitative feedback.

34. Design is everyone’s responsibility.

35. Design often begins without any designer input.

36. Beware of design by committee.

37. Beware of
 drive-by comments.

38. Design should be an open process.

39. Open design is the future.

40. Open design is really hard.

41. Open design requires making at paradigm shift.

42. Open design means showing work early.

43. Open design means accepting imperfection.

44. Open design helps build empathy.

45. Open design means articulating design decisions.

46. Open design means sacrificing your pride.

47. Open design means trusting people.

48. Open design means being respectful.

49. Open design takes constant work.

50. None

51. Thanks! coby@github.com @cobyism