Stealing for Fun and Profit! PDX

Objective-C's a lovely language and Cocoa provides some great frameworks, but there's a ton we can learn from other programming languages and communities. We'll look at how other programming communities solve some common problems and what we can steal from them to make Cocoa development better.

Transcript

1. (Hi there.)
2. Josh Abernathy @joshaber
5. Stealing for and FUN PROFIT
6. STEALING Let’s talk about
10. STEALING:
11. "We have always been shameless about stealing great ideas."
12. "We have always been shameless about stealing great ideas." — Steve Jobs
14. "Good artists copy, great artists steal."
15. "Good artists copy, great artists steal." — Picasso
16. "Good artists copy, great artists steal." — Picasso NOPE
17. STEALING:
18. “To use, appropriate, or preempt the use of another's idea, especially to one's own advantage [...]”
19. Why We Should STEAL
20. We’re all in this TOGETHER
21. Stand on the shoulders of GIANTS
22. When we’re not solving problems, we’re WASTING TIME
23. Why We Don’t STEAL
26. NIH (Not Invented Here)
27. NIIC (Not Invented In Cupertino)
28. Culture
29. Tools
30. Trust
31. You can only steal What you know
32. How to STEAL
33. “To use, appropriate, or preempt the use of another's idea, especially to one's own advantage [...].”
34. Do it the Cocoa Way®
35. (Or don’t.)
36. Underscore.m:
40. What to STEAL
41. Backbone.js
42. Bindings Why: Simple persistence Model collections
45. (See github/Mantle)
46. MVVM (Model-View-ViewModel-lol-wtf-bbq-brb-ftw)
47. Better separation Why: Easier unit testing
48. Rx (Reactive Extensions)
49. Expressive Why: Less state Better code locality
51. (BTW, I already stole Rx.)
52. Persistent Data Structures
53. Safer code Why: “Simpler”
54. Probably everything from Clojure
55. Because it’s awesome Why:
56. Go forth and STEAL
57. (The End.)