r/androiddev • u/amranya • 13h ago

Question [ Removed by moderator ]

[removed] — view removed post

18 Upvotes

85% Upvoted

11 comments sorted by

•

u/androiddev-ModTeam 5h ago

If you have general questions regarding education or career advice, there are many many resources available online. These questions are very common; please make use of the available online resources and recommendations.

If you would like a place to start, please check out our wiki:

https://www.reddit.com/r/androiddev/wiki/index/getting-started/

22

u/Ok_Possible_2260 13h ago

There's only one way you become good at something, it's doing it. Build projects.

1

u/amranya 12h ago

but how can i know i'm doing it right? also how can i know something i'm not even aware of? like recently i found out that coroutines use something called state machine, i don't even know what is it, and found out same concept used in orbit mvi. also how to know deeply how network api calls work aside from using a library like retrofit? like you know enough about it that you can create yours, databases etc.

9

u/shiny0metal0ass 12h ago

Lol honestly? You fuck up.

Build an app with shitty state to learn how to manage it.

Build an app with inefficient API calls to learn how to do them better.

Build a database that scales terribly and is full of broken and awful relationships to learn how to manage data better.

I'm a very competent engineer. It is because I've spent 10 years fucking shit up in different ways and know better.

1

u/Ok_Possible_2260 12h ago

People give you money.

3

u/programadorthi 12h ago

Working in startups and avoiding big techs in the beginning. Small size companies/projects have a lot of opportunities to learn and become a good SE.

2

u/ZeikCallaway 8h ago

As someone who's done Android for a decade and only ever been a mid level engineer, I can't tell you. I can only tell you what not to do. A lot of the real challenge I've seen isn't really the code, it's more dealing with other teams to get things made in a timely manner that isn't going to break something else later.

1

u/AutoModerator 13h ago

Please note that we also have a very active Discord server where you can interact directly with other community members!

Join us on Discord

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/Opulence_Deficit 8h ago

Good for whom?

Just do whatever tasks are thrown at you, as straightforward as you can. That's THE best engineer, according to PMs.

0

u/MikeSawy3r 9h ago

Nowadays??? It's not so much about code it's about product thinking. AI is doing most of the coding
I say build and release. Let it burn. learn and iterate.

The most valuable thing you can learn is to see how the larger the project the easier for it to break. And the better you are at spotting the breaking points before they break the better you become as an engineer. Learning taste in state management, when to break things apart into smaller chunks and when it's acceptable for things to look awful is the skill everyone is searching for.

It really helps though if you are to build a few small projects by hand to see how the world work and make AI your partner where you discuss concepts and implementation.

And one final thing get a job, internship, unpaid paid it doesn't matter. The best way to learn is to do it in a good team where they have the patience to guide you through it. And reject your PRs with good comments. Unless you can't then building on your own should be fine until you find a good team fit