Working together
Jorge Juan Barroso Carmona
[email protected]
@flipper83
+JorgeJBarroso
Android Expert
Android GDE
Slide 2
Slide 2 text
Basho. Poet
Karumi is the beauty of ordinary things spoken of in
a simple way.
Slide 3
Slide 3 text
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
Slide 4
Slide 4 text
Define together
Slide 5
Slide 5 text
No content
Slide 6
Slide 6 text
Everybody must
understand the product
Slide 7
Slide 7 text
The message must be
concise and clear
Slide 8
Slide 8 text
No content
Slide 9
Slide 9 text
No content
Slide 10
Slide 10 text
No content
Slide 11
Slide 11 text
No content
Slide 12
Slide 12 text
No content
Slide 13
Slide 13 text
Iterate all together.
From paper to final code.
Slide 14
Slide 14 text
MVP
Slide 15
Slide 15 text
Talk with your designer.
Sketch + Zeplin.
Proto.io, invision, mockinbird…
Slide 16
Slide 16 text
Working with branches
Slide 17
Slide 17 text
Master
branch1
Slide 18
Slide 18 text
Master
branch1
branch2
Slide 19
Slide 19 text
Master
branch 1
branch 2
branch 1.1
Slide 20
Slide 20 text
Master
branch 1
branch 2
branch 1.1
Slide 21
Slide 21 text
Master
branch 1
branch 2
branch 1.1
merge
Slide 22
Slide 22 text
Master
branch 1
branch 2
branch 1.1
merge
Slide 23
Slide 23 text
Master
branch 1
branch 2
branch 1.1
merge
to market
tag
release
Slide 24
Slide 24 text
Microcommits.
One commit. one thing.
Slide 25
Slide 25 text
Write complete descriptions.
Slide 26
Slide 26 text
Code Reviews
Slide 27
Slide 27 text
Code Reviews must be
mandatory
Slide 28
Slide 28 text
At least two engineers review
your code.
Slide 29
Slide 29 text
Review guidelines, Code
smells, Naming, DRY, Test
quality and give positive
feedback
Slide 30
Slide 30 text
Define a glossary with
application terms.
Slide 31
Slide 31 text
Code reviews are about your
code not about you. It’s
nothing personal.
Slide 32
Slide 32 text
Don’t accept a code review
without tests.
Slide 33
Slide 33 text
Static analysis
Slide 34
Slide 34 text
Checkstyle is your tool.
Slide 35
Slide 35 text
Follow your own guidelines.
You can use the ones from
Google or Square as an
starting point
Slide 36
Slide 36 text
Make it easy to read the code
and talk about it
Slide 37
Slide 37 text
Make it easy to merge code
Slide 38
Slide 38 text
Automatize your tasks
Slide 39
Slide 39 text
Run all tests and check style
Continous integration
Travis, jenkins…
Slide 40
Slide 40 text
You can automatize other
tasks outside office hours.
Slide 41
Slide 41 text
Continuous deployment with
Fastlane
Upload releases and betas
automatically
Slide 42
Slide 42 text
Generate nightly builds for
your team
Slide 43
Slide 43 text
Pull request
Slide 44
Slide 44 text
Nobody commits to the
master branch
Slide 45
Slide 45 text
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
Slide 46
Slide 46 text
Be a good partner
Slide 47
Slide 47 text
you are not your code. This is
our code.
Slide 48
Slide 48 text
Help your partners.
Request help if you need it
Slide 49
Slide 49 text
Listen to everyone.
Beginner mind
Slide 50
Slide 50 text
Learn something new every
day
Slide 51
Slide 51 text
Make your team better
Slide 52
Slide 52 text
Lead by example
Slide 53
Slide 53 text
Don’t break the rules
Slide 54
Slide 54 text
No ego
Slide 55
Slide 55 text
Says “No”
Slide 56
Slide 56 text
No content
Slide 57
Slide 57 text
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
Slide 58
Slide 58 text
Find me
I am very social!
[email protected]
@flipper83
+JorgeJBarroso
Questions?