Day 1/100: Going Back to Basics as a Senior Android Dev

Five years. That's how long I've been writing Android code. I've survived the transition from Java to Kotlin, from XML layouts to Jetpack Compose, from AsyncTask to Coroutines. I've shipped apps to millions of users, debugged production crashes at 2 AM, and mentored junior developers. So why am I starting a series called "100 Days to Senior Android Engineer" ? The moment that started this A few weeks ago, a colleague asked me something that should've been simple: "Hey, can you explain exactly what happens to a running coroutine when the system kills our process?" I opened my mouth. I closed it. I knew the answer — survived state gets lost, ViewModel is gone, onSaveInstanceState is your last checkpoint. I've handled this in production code dozens of times. But I couldn't explain the mechanism . The chain of events. The why . That gap bothered me more than I expected. The real reason seniors go back to basics There's a difference between knowing how to use a tool and understanding why th