Android

Recently, there is a trend that code is not an asset. Let's think about it!

Here, I have to write this one, because I noticed I didn't cover everything in my previous post Dependency inversion principle.

This article has two goals. Emphasizing the "Dependency Inversion Principle", DIP, and making it more exciting by explaining who I am and what kind of job I'm looking for!

After introducing Jetpack Compose to the Android ecosystem by Google, people slowly realize that old MVVM architecture, which after trying to tie it up to Compose we call it Android Architecture Components (AAC) ViewModel, is raising some lifecycle problems. This post is about the problem and its possible solution.

This article focus on Android projects, but the idea can be applied on other kind of projects too. To start, let's explain all these concepts then try to figure out their relationship.

As the modularization of a big app may take years to finish, it’s hard to see the effect of this process on build time any time soon. At iFood we practiced the following method to have a faster rebuild on moularized features.

This post is on the tail of Railway Oriented Programming in Kotlin by Antony Harfield. So you need to read it first and continue here. As it’s obvious I really liked it and tried it out. It needs every process have a result like The generic result

Do you use more than two versions of implementation when you’re A/B testing? Or do you implement them with some if conditions in your Presentes, ViewModels, etc? If yes, you’re probably A/B testing wrong!