@dj_gostosa
Lots of code solving imaginary future problems, anticipating change that may never come or will be completely different than expected (because predicting the future is hard).
@ChrisArter
When refactoring code, you have to be focused on clarity and succinctness. Not sure that gratification is a measure of the quality of your coding.
@ChrisArter
Actually yes, removed layer-based modularization and replaced it with component-based modularization.
Also replaced type-based Dagger module splits with feature-based organization of Dagger modules. Suddenly you needed to change only 1 instead of 8 when adding a new screen. 😎
@ChrisArter
You just described my week buddy! It feels a bit sad to remove code you spent so much time on, but also really really nice to know you won't need to worry about that mess anymore!