Stop Debating in Code Reviews. Start Enforcing with Lint Rules.
Have you ever seen code review comments like these?
- “Hey Jane, ideally the ViewModel shouldn't interact directly with the Repository. It’s best to communicate with a UseCase instead.”
- “Didn’t we recently agree that UseCases should only expose a single function?”
- “Wait I’m confused, are we supposed to access String resources directly from ViewModels?”
Do you know what are these? These are all code review smells! As engineers, we're not designed to remember every detail in the architecture of our projects. But fortunately, we can write the lint rules that will do that for us.
Meet Konsist - a long-overdue tool on Android that simplifies writing lint rules by reimagining them as unit tests, eliminating the steep learning curve of existing linters.
Join this session to learn how to:
1. Write lint rules that enforce your team's architectural standards and best practices, in the form of unit tests.
2. Use lint rules to prevent bugs early in the development process.
3. Integrate these lint rules into your CI/CD pipeline.
Stelios is a Staff Engineer at Perry Street Software, publisher of the LGBTQ+ dating apps SCRUFF and Jack’d, serving a community of more than 30 million members worldwide.
He has been professionally working with Android for more than 10 years, since the release of Android Gingerbread. He’s passionate about Clean Architecture, Domain-Driven Design, Test-Driven Development and Behavior-Driven Development.
