tl;dr Kotlin properties are awesome and super powerful, but each form comes with a bunch of gotchas. Make sure you fully understand them…
Developers love properties in Kotlin, but a property is not always the right choice. Getting carried away can be risky, so when should we avoid properties?
Many people love by lazy, but it's easy to underestimate and misuse it. When should you use lateinit, and when is by lazy a better choice, as an Android developer?
In this series we're going to be looking at a few common patterns I have seen Android developers use in Kotlin, and see what's the good and bad in each, and when to use them.
We know about static analysis and CircleCI - now it's time to get into the nitty-gritty of configuring your CI.
If you want a CI for your projects but never knew how to, or thought you could not afford it, this post shows how to get a comprehensive setup - for free! - using CircleCI.