Last updated: 4 months ago
Pair programming is two engineers doing a single engineer’s work.
Writing tests before writing the code is slow.
Continuous deployment is too much of a hassle - just archive an .ipa on your local machine and upload it manually to iTunes connect.
Are these facts or myths? I used pair programming and TDD (Test Driven Development) techniques for 8 hours a day for 17 months. It allowed me not only speak Objective-C and Swift better but be more efficient in writing software. The technology industry is competitive and teams that can iterate quickly to a valuable product will win. In the talk, I will break some myths about the pair programming and TDD and share what they taught me.