Working together

This talk is about teams, processes, branches, code reviews and how to improve as a team working together.

Transcript

1. Working together Jorge Juan Barroso Carmona jorge@karumi.com @flipper83 +JorgeJBarroso Android Expert Android GDE
2. Basho. Poet Karumi is the beauty of ordinary things spoken of in a simple way.
3. Adam Tornhill “Most software is created by teams. Teams are most effective when the team members collaborate professionally. It is unprofessional to be a loner or a recluse on a team.” Uncle Bob
4. Define together
6. Everybody must understand the product
7. The message must be concise and clear
13. Iterate all together. From paper to final code.
14. MVP
15. Talk with your designer. Sketch + Zeplin. Proto.io, invision, mockinbird…
16. Working with branches
17. Master branch1
18. Master branch1 branch2
19. Master branch 1 branch 2 branch 1.1
20. Master branch 1 branch 2 branch 1.1
21. Master branch 1 branch 2 branch 1.1 merge
22. Master branch 1 branch 2 branch 1.1 merge
23. Master branch 1 branch 2 branch 1.1 merge to market tag release
24. Microcommits. One commit. one thing.
25. Write complete descriptions.
26. Code Reviews
27. Code Reviews must be mandatory
28. At least two engineers review your code.
29. Review guidelines, Code smells, Naming, DRY, Test quality and give positive feedback
30. Define a glossary with application terms.
31. Code reviews are about your code not about you. It’s nothing personal.
32. Don’t accept a code review without tests.
33. Static analysis
34. Checkstyle is your tool.
35. Follow your own guidelines. You can use the ones from Google or Square as an starting point
36. Make it easy to read the code and talk about it
37. Make it easy to merge code
38. Automatize your tasks
39. Run all tests and check style Continous integration Travis, jenkins…
40. You can automatize other tasks outside office hours.
41. Continuous deployment with Fastlane Upload releases and betas automatically
42. Generate nightly builds for your team
43. Pull request
44. Nobody commits to the master branch
45. A valid pull request needs to: - Pass the code review process - Have all the tests passing in the CI infrastructure - Have the code style validated in the CI infrastructure
46. Be a good partner
47. you are not your code. This is our code.
48. Help your partners. Request help if you need it
49. Listen to everyone. Beginner mind
50. Learn something new every day
51. Make your team better
52. Lead by example
53. Don’t break the rules
54. No ego
55. Says “No”
57. Bibliography They’re the cracks! LocoRoco Postmortem:Making Happiness into Gameplay. Tsutomu Kouno. 2007 One-Page Designs. Stone Librande GDC. 2010 Clean Code. Uncle Bob. 2008 The Clean Coder. Uncle Bob. 2011 The One Minute Manager. Kenneth Blanchard and Spencer Johnson
58. Find me I am very social! jorge@karumi.com @flipper83 +JorgeJBarroso Questions?