How do android developers remember all the in - built methods, inner classes, interfaces... In android studio?

Question

0.00/5 (No votes)

See more:

I have been learning android dev in android studio for the past 20 days from the book "Head First Android Development" and as I am starting new chapters, there are always new methods, inner classes... of new widgets getting introduced to me and it's getting hard to memorize all these stuff!

Can someone give me some advice? In serious need of help.

Do all the professional android developers keep a guide with them while they are developing apps?

What I have tried:

I have tried many things but none of them are working.

Posted 28-Aug-21 3:51am

Darshil Shah 2021

Updated 28-Aug-21 10:17am

Add a Solution

Comments

Richard MacCutchan 28-Aug-21 10:34am

As computer languages and frameworks get ever more sophisticated it is harder to remember everything. The important thing is to know where to look for the information. A printed book is always useful, and there are also plenty of online references.

Darshil Shah 2021 29-Aug-21 12:53pm

Is it normal for professional android developers to get stuck / forget stuff while they are developing apps and then Google it to get the answer? Is that really what happens?

Richard MacCutchan 30-Aug-21 3:58am

No, it is normal for developers in any language. There is far too much information for anyone to be able to commit it all to memory. The key is knowing where to look when you cannot remember something.

Darshil Shah 2021 30-Aug-21 8:00am

Thanks, Richard. Your reply was a great help. Again, Thank you!

[no name] 28-Aug-21 11:00am

You don't. You just have to master the ability to search for what you need in the resources available. And then realize there's usually more than one way to get a thing done; some easier; some harder.

Darshil Shah 2021 29-Aug-21 12:53pm

Is it normal for professional android developers to get stuck / forget stuff while they are developing apps and then Google it to get the answer? Is that really what happens?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2021-08-28T10:17:00

This isn't a problem that is specific to Java, or Android: modern frameworks are very complex and full featured with the result that it's pretty much impossible to remember everything in it in detail. Or at least, that certainly the case for me!

What I do remember in detail is the stuff I use everyday, the rest is mostly a "I know it exists" kind of memory - so when I do need it I know that I can find it pretty quickly. We can't know everything, but if we haven't been exposed to it at all, we just don't know it exists - that's why the "pick it up as you go along" method so popular among Youtube tutorial viewers is so ineffective. A book is a good idea (but not generally as good as course) as long as you do all the exercises to "embed" the information in your brain so you will t lest remember that it exists!

If it's any consolation, I've needed something complex, vaguely remembered seeing something like it so a quick google and I'm at an article or tip here on Codeproject. A quick read and it does what I wanted ... then I notice I wrote it a couple of years ago ... :blush: