This is a great question to refresh and revise what I have learned over the years from my ex-colleagues especially @inyaki_mwc & @jperezalv
I'll try to summarize what usual suspects I can recall in the 🧵

https://twitter.com/ragunathjawahar/status/1593149277366546434

Usually, the answer lies in your build scans which is an amazing feature of the #Gradle build tool.
A Gradle build scan tells you how much time was spent in each of the three phases of the build lifecycle namely:

👉 Initialization
👉 Configuration
👉 Execution

Been interviewing candidates for senior android roles for a while now, here at Tinder. Here’s are some thoughts and learnings —
Not going to be company specific 1/n 🧵 Majority of the candidates want to solve the problem right away, as soon as they see it. This is basic human nature but the people who didn’t take this approach most of the time did really well. Let’s talk about why I feel this hurts you as a candidate