[ ] Update lesson plan to talk more generally about abstraction/encapsulation
[ ] Introduce Service classes
[ ] Introduce the idea of a PORO, and the concept of deserialization and using our own domain objects
[ ] Discuss other options for removing logic from controllers -- facades, nested POROs, other utility classes. No need to only stick to facade. IMO this section should be VERY LIGHT
[ ] Update lesson repo/exercises -- Check out this consuming API with Ruby lesson they'll be doing for intermission here or if it's already merged, it's in the lessons directory of the M3 directory
Notes:
We don't need such a heavy emphasis on this in the new program. Make this content lighter. 2 hour class max
Existing lesson - https://backend.turing.edu/module3/lessons/refactoring_api_consumption
Notes:
We don't need such a heavy emphasis on this in the new program. Make this content lighter. 2 hour class max