Consistency Principle
summary
Claim: architectural inconsistencies (duplicate verticals), not raw complexity, kill developer velocity. Concrete pattern: treat each layer as an API and minimize entry points — example refactor turns a NetworkService from many methods into one generic get(resource) plus RemoteResource objects that build requests, handle headers and JSON deserialization. Tools and migrations shown: URLSession, Localytics → Mixpanel coexisting, swapping in Alamofire becomes one-file change. Applied on a nine-year app: replaced networking layer, reduced crashes and restored delivery speed.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:52Dependency Decisions
- 8:02Longevity
- 11:53Consistency Principle
- 15:24Layers
- 17:04Network Service
- 19:23Minimize Entry Points
related talks
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
26mAdapting to change: design patterns in Swift
51mA Contrarian View of Software Architecture
01h 01mGuide to Destroying Codebases the Demise of Clever Code
50mThe Unbearable Weight of Architecture
40mMobiconf 2018: John Sundell, Swift by Sundell
01h 29mMonolithic Delivery
46mAchieving an evolutionary architecture through simplicity