Dan Tech Academy
After this lesson you will
  • Verify that :domain is pure with the build file and git grep
  • Use empty(), require and classifying errors once at the boundary
  • Recognize when not to add a layer, and weigh trade-offs like error messages in the domain
Duration25 min
DifficultyIntermediate

Best Practices And Anti-Patterns

Best Practices And Anti-Patterns in the Mobile Action Pro course.

What this lesson covers
  1. 01Lesson Goal
  2. 02Part 1: A Truly Pure Domain, And Provably So
  3. 03Part 2: Non-Null Models With empty()
  4. 04Part 3: Invariants With require()
  5. 05Part 4: Classify Errors Once, At The Boundary
  6. 06Part 5: An Explicit Composition Root
  7. 07Part 6: Don't Add Layers You Don't Need
  8. 08Practice Exercise
  9. 09Code Reading Path
  10. 10Signs To Avoid
  11. 11References
  12. 12Key Points

Topics: kotlin, 06-clean-architecture

12 sections left in this lessonUnlock all of Mobile Action ProLesson Goal, Part 1: A Truly Pure Domain, And Provably So, … — plus 114 lessons in this course, source code and checklists.
Unlock Mobile Action ProOne-time payment — lifetime access — 7-day money-back. Already purchased? Sign in
Sign in