Laziness-Driven Development in iOS - CocoaConf Boston, September 2015

My talk on how Laziness is secretly the best way to code.

Links galore at the end!

Transcript

1. Laziness-Driven Development in iOS CocoaConf Boston | September 2015 | by Ellen Shapiro vokal.io | justhum.com | designatednerd.com | @designatednerd
2. What is Laziness- Driven Development?
3. The laziness long game.
4. What is lazy, but is NOT Laziness-Driven Development?
5. Copy Pasta
6. Code without tests
7. Code which is fast to write, but impossible to read
8. Using libraries for every possible task
9. What is Laziness-Driven Development? » Smart reuse of code » Clear, Readable code » Removal of Stringly-typed code » Making smart decisions today to save yourself time and heartache tomorrow
10. The primary philosophy of Laziness-Driven Development:
11. Eventually, You're going to screw something up
12. only screw it up once. Then, you only have to fix it once.
13. Introductory Laziness-Driven development: Inheritance & MV*
14. Keep code separated by its purpose
15. Keep code with the same purpose centralized
16. Aren't those just Best Practices?
17. YES
18. YEs, but they are only the beginning
19. Beginning Laziness-Driven development: Constants, Structs and Enums
20. Stringly-typed code Sucks
22. espeshuly if u cant spel... (this is from just one repo)
23. It's the worst
24. String Constants: The Cure For Speling Problums
25. Before:
26. After:
27. constants: Not just for strings self.viewWidth = 74; vs. self.viewWidth = kProfileViewWidth;
28. Enums: Even lazier constants
33. (#pandering)
34. Beginning Laziness-Driven development: Comment And Name Clearly
35. readability
36. "programs must be written for people to read, and only incidentally for machines to execute."
37. Variable naming BAD: UIView *v, CGPoint pt BETTER: UIView *profileView, CGPoint profileOrigin
38. Method Naming Objective-C: extremelyLongAndDescriptiveMethodOnLabel:label withParameter:parameter andCompletionBlock:completion Swift: shortButClearMethodOnLabel(label, param, completion)
39. Benefits of clear naming
43. Some people say: "Comments Lie, Code Doesn't"
44. If you update code without updating comments, you're doing it wrong
45. //TODO: Write better comments
46. What < Why
47. Leave The Campsite Code cleaner than you found it
48. the goal of good comments and clear naming is the same: Future laziness for you
49. Beginning Laziness-Driven development: Unit Testing
50. Testing stuff manually is a pain. (Repeat ad nauseam until it's fixed)
51. Remember: Your computer is an awesome robot you can use to do your evil bidding
55. Intermediate Laziness-Driven development: Categories & Extensions
56. Adding functionality to existing objects (and also to structs in Swift)
57. Objective-C: Categories UIView+XYZApp: - (void)xyz_circleify { self.layer.cornerRadius = CGRectGetWidth(self.frame) / 2; self.clipsToBounds = YES; }
58. Watch for method name collsions
59. Swift: Extensions MyViewExtension: extension UIView { public func xyz_circleify() { layer.cornerRadius = CGRectGetWidth(frame) / 2 clipsToBounds = true } }
60. Watch for method name collsions even in Swift
61. Intermediate Laziness-Driven development: Laziness-Enhancing Tools
62. Alcatraz: Xcode plugins for all!
63. Plugins Before Alcatraz » Download project » Build, run, install, » Restart Xcode, » Do the hokey pokey and turn yourself about. » Uninstall by hunting down obscure folder and then forgetting what the hell you were doing in there.
64. Plugins AFTER Alcatraz » Push button, install plugin. » Push other button to see plugin page. » Search plugins easily. » Push button, uninstall plugin. !
65. Laziness-Enhancing Plugins
66. VVDocumenter
67. xTODO
68. BBFullIssue Navigator
69. FuzzyAutocomplete
70. SCXcodeMiniMap
72. A place for ideas
73. Get a better idea of what is simple and what is not
74. MOGenerator - Make Core Data less painful
75. MOGenerator Kills Stringly-Typed Code just to watch it die
76. Lazier Code with MOGenerator
77. Advanced Laziness-Driven development: UI Testing
78. KIF
79. KIF
80. Xcode 7 UI TESTING
81. All UI testing
82. UI Testing Gotchas
83. Advanced Laziness-Driven development: Adopting laziness techniques from other languges
84. Android
87. Figure out how to take the theory and use it in an iOS-friendly way
88. Caution: Take care that you're bringing things over as supplements.
89. Don't try to force a new language or platform to fit what you already know
90. Advanced Laziness-Driven development: Writing Your own Laziness-Enhancing Tools
91. When Should You write Your own tools?
93. (Achtung! shameless self-promotion)
94. My Experience Writing Tools
95. Cat2Cat Asset Catalog To Category Instead of writing: [UIImage imageNamed:@"My Image Name"]; you can write: [UIImage ac_My_Image_Name];
96. How is this lazier?
98. XcodeautoBasher
100. in conclusion » Centralize your code, make it easy to read, and keep it separated by purpose, so it's easy to fix. » Get rid of stringly-typed code so it's harder to break in the first place. » Use the tools other people have built to enhance your laziness, or build new tools yourself. » Best practices are secretly the lazy way to code.
101. Questions?
102. Thank you!
103. Links » Alcatraz: http://alcatraz.io/ » Cocoa Controls: https://www.cocoacontrols.com/
104. Code Generation Tools » MOGenerator: https://github.com/rentzsch/ mogenerator » Cat2Cat: https://github.com/vokal/Cat2Cat » objc codegenutils: https://github.com/square/objc- codegenutils/
105. Alcatraz Plugins » https://github.com/vokal/XcodeAutoBasher » https://github.com/onevcat/VVDocumenter-Xcode » https://github.com/trawor/XToDo » https://github.com/neonichu/BBUFullIssueNavigator » https://github.com/FuzzyAutocomplete/ FuzzyAutocompletePlugin » https://github.com/stefanceriu/SCXcodeMiniMap
106. image credits » Luca Nebuloni, Pasta with finocciona: https:// www.flickr.com/photos/nebulux/10708289086 » Tom Bech, Eurasian Wolf: https://www.flickr.com/ photos/viatorius/9358589025 » Michael D Beckwith, The Leeds Library: https:// www.flickr.com/photos/118118485@N05/16438065636/