Hey guys. What good reads have absolutely changed ...

# android-architecture

[Ofir Bar]

Hey guys.
What good reads have absolutely changed the way you think about architecture/design?
Assuming I am a junior developer, I already know “MVVM”, and I can write big applications, but I find myself writing repeated code.
I feel like I am following trends and not having a good understanding of design and best practices.

Right now - I am reading effective kotlin, is it the route to go?. What I am worried about is that I see other senior developers being able to write super smart generic code, but I am unsure as if this is something acceptable within the industry or are those “hacks” might get other developers confused or is it just me

[Anastasia Finogenova]

I have seen it both ways, some devs right smart code but some abstract to abstract and then you jump through 5 helper classes utls and interfaces to understand where this bug is actually coming from

[Anastasia Finogenova]

Just read more and trust time, you will get it, just need more time to learn, check Google example repos (sunflower, patch apps)

[Anastasia Finogenova]

And a shameless plug for you ....😉 https://proandroiddev.com/our-way-to-mvvmi-and-mistakes-we-made-when-implementing-mvvm-5f5448b5ad50

[tschuchort]

My advice is to pick the language that is the most different from what you know and try to understand why.

[Ofir Bar]

Thank you dear @Anastasia Finogenova

[Ianmedeiros]

I recommend a book that is not android related: https://www.manning.com/books/dependency-injection-principles-practices-patterns

[Ianmedeiros]

It’s not about dependency injection in C#, but overall patterns / anti-patterns and concepts

[Anastasia Finogenova]

There is also a great boot Design Pattern by the 6 (I don't recollect the names)

[Ianmedeiros]

gang of 4?

[Anastasia Finogenova]

Lol yes

[Ianmedeiros]

This Dependency Injection book, for me, is one of the best books on building loose coupled code

[Ianmedeiros]

It’s really good.

[Ianmedeiros]

About design patterns, i think this one is better if it’s your first read on the subject: https://www.amazon.com/Head-First-Design-Patterns-Brain-Friendly/dp/0596007124/ref=sr_1_2?crid=3GGAQLG89TKAV&keywords=design+patterns&qid=1581964771&sprefix=design+patterns%2Caps%2C277&sr=8-2

[codeslubber]

vote for the original over head first..

[Brendan Weinstein]

https://overreacted.io/goodbye-clean-code/ -- sometimes the reusable code is worse.

It is great to work on a side project over the long run. 6-9 months later when you look back at your code you may or may not think it is good. It may not be good and you rewrite it another way. Then you revisit a few months later and realize some complicated piece is just going to be complicated no matter what.