The Project Template
summary
Over 20 open source projects reach about 80,000 teams; the concrete recommendations are: use Swift Package Manager to force modularization and reduce PBX files to a single host, write custom SwiftLint rules (some projects use 30+) to automate PR feedback, generate code with sorcery templates instead of fragile macros, avoid running external generators on every build (running them 200–400 times/day added hours), detect leaks with a lifetime tracker (e.g. precache 3 articles, flag a 4th), and enable hot reload with inject.
AI-written summary · about
chapters (9)
- 0:00Introduction and topics
- 1:43Project organization
- 4:58Automated build tools
- 8:19Bugs and debugging
- 11:21Developer tools
- 14:40Improving iteration speed
- 20:07Testing strategies
- 25:29Useful community libraries
- 29:29Conclusion and Q&A
related talks
33mScaling Swift Development
37mCut costs, not corners: Master modularization with SPM
42mSplitting Monolithic Swift Code Base Into Modules
37mBeyond Xcode
44mSwift Packages - Dependency Management of the Future
24mOpen Source & Swift
32mSpeeding up the build process of a monolithic application
43mFrom Modularization to Clang and Back