Philipp Lackner shows a ~20,000-line Kotlin cloud file manager app built almost entirely by AI agents in two or three working days, then argues the only reason it works is that he has hand-written every one of those patterns hundreds of times before. His point: AI agents are now mandatory for a coding career, but reading AI-generated code teaches you almost nothing, so you should only delegate concepts you already understand deeply. His test is whether you could pass a spontaneous coding interview on a topic; if not, write that code yourself first.
- The demo app is a cloud file manager with zero-knowledge authentication, currently around 20,000 lines of Kotlin and expected to reach 100,000–150,000, with 99% of the code written by AI agents in two to three working days.
- Lackner is blunt that developers who don't adopt AI-driven development are 'screwed' if they want coding as a career — the argument is about sequencing, not avoidance.
- His leverage comes from repetition: he's set up Room databases ~100 times, multi-module structures 20–30 times, Gradle convention plugins ~20 times, and written over 100,000 lines of Compose UI and 2,000+ test cases.
- That prior experience lets him spot roughly 80% of issues instantly during review and write agent skills that encode his own conventions, architecture, and Compose rules.
- Without hands-on experience you can't tell when an AI is oversimplifying or over-complicating a problem, especially on fundamentals like architecture and system design.
- Reading code — including AI output — works like reading a book: you retain little. Writing it, debugging it, reading stack traces and error messages yourself is what makes knowledge stick.
- His threshold for delegating a topic to an agent: you could walk into a spontaneous coding interview on it today and nail it without preparation.
- His mentorship program's first month bans agents entirely and requires hand-typing an app from scratch, so they diagnose the mentee's gaps rather than the agent's.
- Agent-generated code works fine in small apps, but at scale unaddressed fundamental problems compound into spaghetti code and bugs, at which point the agents themselves start behaving strangely.
This is the pivot of the whole argument — the impressive AI result is downstream of years of manual repetition.
In no world, any developer would have been able to build what I have here in two or three working days by hand typing the code. But here comes the thing. The only reason I'm able to do this in two to three working days is because all of this code, all of these concepts used, those are things that I have written a gazillion times myself in the past.
A concrete, usable rule for deciding which work you can hand to an agent and which you still need to type yourself.
Once you are in the position where you could have a coding interview right now about a specific topic like implementing a Room DB and you would feel very well that you would nail that interview spontaneously right now without preparing for that — that's the point where it's completely fine to work with AI to generate the code for this technology.
Writing something yourself just activates completely different regions in your brain than reading something.
Working with AI is really just like reading a book. You will read a lot of code, you will review a lot of code, and reading that code is not what makes new things stick.
Everybody can use an agent in a small app, but the challenge is how you use it in a production environment.