Start Here: 100 Posts on Senior Android Engineering (and Working With AI)
A 100-post series sharing 12 years of production Android experience — Compose internals, coroutines, performance, architecture, and how a senior engineer actually works with AI. Here's the plan.
Hessam Rastegari
Senior Android Developer · 12 years shipping Android
I've spent twelve years building Android — from early Java apps to Kotlin Multiplatform, from Android TV and OTT streaming to AI-powered products. Along the way I've accumulated the kind of knowledge that doesn't fit in documentation: the trade-offs, the failure modes, the "why" behind the patterns. This series is me writing it down, one focused post at a time.
The plan
100 posts. One every couple of days. Senior-level and code-first. No beginner tutorials — these are written for engineers who already ship, and for the people who lead them. Each post comes with a short, scannable summary and a set of slides, plus a full write-up here on the site.
What it covers
- Jetpack Compose internals — recomposition, stability, and the performance work that actually moves the needle.
- Kotlin coroutines & Flow — structured concurrency, cancellation, and the concurrency bugs that hide in "we use coroutines."
- Performance & release engineering — startup, baseline profiles, R8, 99.9% crash-free.
- Architecture — Clean Architecture trade-offs, modularization, and keeping a codebase sane as a team grows.
- Testing, CI/CD, Android TV/OTT, Kotlin Multiplatform — the breadth of real product work.
The part I care most about: working with AI
There's a lot of noise about AI and almost no honest, senior-level content about how it fits into a real Android workflow. So a recurring thread in this series is exactly that: how I use AI as an experienced engineer — to review a diff, to refactor legacy Java to Kotlin safely, to generate tests worth keeping, to reason about a tricky concurrency bug. Not "AI will replace developers," and not blind vibe-coding — the actual, disciplined workflow that makes a senior engineer faster without giving up judgment. Several posts take a normal Android topic and show how to approach it with AI as a pair.
Why I'm doing this
Partly to give back — the Android community taught me everything. Partly because writing forces clarity. And partly because the best way to show what you know is to teach it. If any of this helps you ship a better app, that's the whole point.
Follow along here or on LinkedIn. Let's raise the floor together.