Ramon and Passy continue on their journey of explaining how big applications are built on the example of Twitter for Android and iOS. The main topic this time is code review. How do you write patches that are easy to review, structure your workflow and which guidelines do you follow when evaluating others' work?

Topics

• YakYak authentication problems
• The Fall 2016 Special Apple Event
• Ramon's (un)success story of switching to a Nexus phone for a week
• Passy's small Haskell web service rendering PNGs and SVGs (on GitHub)
• It's Passy's last week at Twitter. :( But Strictly Untyped shall persevere!
• 00:19:45 - Code Review at scale

Code Review

• Gerrit for code review.
• https://twitter.com/iamdevloper/status/397664295875805184
• IBM's study on effectiveness of big code reviews.
• stacked git for breaking down large patches.

Picks

• Ramon: Game, Inside for PS4
• Passy: Podcast, Magic Read Along
• Ramon: Podcast, Rocket
• Passy: Paper, Type-level Web APIs with Servant