How to Improve Your Mobile Project in 1 Day - A Guide for Everyone
summary
Claims a one‑day lift by adding six concrete tools: a clear readmi 5, a pull‑request template, pinned dependency versions, static analysis (SwiftLint style), Danger checks, and branch protection rules. Implements fixed versions after seeing npm libraries like colors (3 billion downloads) and Faker (300 million) break builds. Pull requests end up blocked until CI is green and conversations are resolved, reviewers are enforced, linters flag changed files only, and the pipeline demonstrably reduces broken merges.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:25Why this talk
- 7:19Good README matters
- 11:14Using pull request templates effectively
- 14:27Package managers
- 18:42Static analysis
- 21:44Danger for PR checks
- 25:17Branch protection rules
- 29:58Tools summary
- 32:05Q&A
related talks
43mScalable Best Practices for Your Development Team
35mQuickly and Safely Refactoring Legacy Code
28mSome small steps for code, One giant leap for quality
20mTesting Complex and Time Critical Projects!
01h 01mA Test a Day Keeps Your Manager Away!
49mBalancing Release & Sprint Delivery Speed with Thorough Testing
32mContinuous Integration and Deployment: Five Lessons Learned
21mSucceed by Failing – A Game Dev’s Journey Into a Mobile Dev Ops Tool Chain