14. • Pass just the meaningful info to a new adapter
• Reduce noise/kill boilerplate
• Don’t repeat ourselves
15. Java version
• Achieved DRY but…
• Far more boilerplate than the original!
• And worse, boilerplate is in calling code rather than
hidden in implementation (anonymous inner
• Conclusion: not worth it. Stick with adapter coupled
to concrete fragments
• Reduce your (Java-imposed) tolerance to
boilerplate. It’s even more of a code smell in Kotlin!
• Lots of language tools to kill boilerplate!
• Passing functions around is new territory, be