Controlling complexity for large iOS projects

Presented at https://www.facebook.com/events/1534925300149432/
This talk discloses some points on bringing dependency hell back under control. It also includes demo of https://github.com/soxjke/WatchDogs

Transcript

1. Controlling complexity for large iOS projects Petro Korienev, iOS Engineer @ Techery
2. DISCLAIMER
3. • Sporadic crashes • Intermittent issues • Hardly debuggable code PROBLEMS WHILE SCALING
4. • Moore’s law (hardware’s getting twice faster every 2 years) WHY DOES IT HAPPEN? • Wirth’s law (software’s getting slower faster than hardware’s getting faster)
5. SO WHY?
6. FEW SLOC FACTS
7. • Complexity growth with time SO,
8. • Control decreases over time • Consequence of growing complexity • Maintainer change • Software is not an IP carrier, author is
9. Here comes TRUST
10. • Trust in community and time-proven solutions • Trust in self TRUST
11. • AFNetworking 2.5.1-2.5.2 • OpenSSL heartbleed • Numerous zero-day exploits • Just bugs TRUST IN COMMUNITY
12. • “I’ve seen stuff like this before” • “This is pretty straightforward” • “If i’d do stuff like this, i’d do this way” TRUST IN SELF
14. • Bugs • Exploits • Limitations • Tech debt Consequences
15. Prefer control over trust CAPTAIN’S VOICE:
16. When the code becomes legacy dependency
17. SOLUTIONS 1. Don’t care of it (Blackboxing) 2. Whiteboxing 3. Get rid of dependencies 4. Grayboxing
18. DON’T CARE OF IT • Simple • Unreliable • Tends to consume time when scaling
19. DON’T CARE OF IT
20. WHITEBOXING
21. WHITEBOXING • Very time-consuming • Reliable after certain effort put • Extremely difficult with closed- source
22. GET RID OF DEPENDENCIES
23. GET RID OF DEPENDENCIES
24. GET RID OF DEPENDENCIES • Sometimes is not applicable • Possible even with closed- source • In moderate scale it’s the best approach to take control
25. GRAYBOXING • Good tradeoff between white- and blackboxing • Flexible • Applicable almost everywhere • Dynamic
26. GRAYBOXING • Idea is to find a right place and inject something validating the correctness of contract • Unlike unit tests, verifies dynamic, run-time behaviour
27. EXAMPLE • https://github.com/soxjke/ WatchDogs
28. PROBLEM • Inconsistency and mess within CoreData across the project • Fake certainty in thread- access
29. SOLUTION AND DEMO
30. THANK YOU FOR YOUR ATTENTION! Q&A TIME
31. YOU CAN FIND ME: • https://github.com/soxjke • https://twitter.com/soxjke • http://stackoverflow.com/users/ 2392973/petro-korienev