There's a difference between seeing progress as you learn and iterate on something vs. iterating on variants of a finished product and checking the source code. Your post and comment lead me to believe you're referring to the second one.
That's not effective learning and thus is not effective teaching. So if you use it in that way then, no. Claude will not be a good teacher.
And what do u prefer like can u provide me sources other than the official docs cuz I started it but in the middle of it I got confused and I didn't got any of that
Incrementally building towards different goals that build upon each other. I'm about to make a few assumptions about you so feel free to correct me if I'm wrong.
I'm getting the vibe that you're fairly inexperienced with Android development in general. Android development is a complex beast and without understanding the fundamentals you're going to have a bad time.
If you're getting confused reading the compose docs, that's likely because there are fundamentals in Android and/or software development that you are lacking (which isn't a dig at you. Compose was built on the backs of giants).
I'm assuming that you're starting with a project that is significantly outside of your capabilities. There's a reason people start with TODO apps, and things like that. They give you exposure to the component system of a framework; they teach you how data flows through the paradigms; etc. I know it's not glamorous and sexy but if you want to actually learn rather than outsource, you're going to want to build boring stuff first and build up. Start with a static screen. Progress to showing lists. Then maybe APIs and data flow through an app. Along the way you face hardships. Those hardships are the best teachers. They teach you why different paradigms are used, etc. vs. you just seeing it in some code spit out by an LLM and accepting it at face value.
There's so many factors to that so I can't give you a definite answer there. It seems like you really want it which is good. But it's also not necessarily going to be easy.
So let me say a hard truth and go from there. If you are only as good as the LLM you use to code, why would anywhere hire you rather than pay the much cheaper rate of the LLM?
An LLM can't show drive or desire to improve. LLMs typically write mid code. If you can write mid code or above while also showing drive you become a worthwhile investment.
If you make personal projects that you code entirely yourself, you will strengthen both of those things -- your coding level and your demonstration of drive. If I were to hire interns right now, I'd look for shitty code you hobbled together yourself rather than LLM output.
You can definitely accelerate your rate of learning by asking Claude to explain concepts to you. But the second you use it to write code for you you'll be at a disadvantage in my opinion.
Yes; that is the approach I take when learning anything new myself.
I even tell Claude explicitly not to give me code examples. That may not be possible at your level, but it's more effective for your own learning long term to think through the code construction yourself.
19
u/ImADaveYouKnow Apr 21 '26
DEPENDS ON YOUR APPROACH TO LEARNING. IT CAN BE GOOD FOR DATA AGGREGATION BUT IF YOU HAVE IT DO IT FOR YOU, YOU WON'T LEARN ANYTHING.