We fell in love with Android development because we love *building* things. Today, AI is aggressively taking over the "creation" part of our role, and we're assuming the job of auditor.

But when you outsource the typing, you outsource the thinking.

So:
* How do we prevent our technical skills from fading?

* How do we maintain true ownership of a codebase when we're not the ones writing it?

* How important, even, are the architecture skills we learned? Why does architecture exist?

In this talk I argue that now, more than ever, good architecture is critical, and that developers should value code quality over velocity.

This talk is a manifesto for the survival of the thinking developer, and for reclaiming the art of software engineering from the trap of mindless code reviews.