In the early stages of my career, I thought completing a task as quickly as possible was what made you a productive developer. I’m sure many of you thought the same, but you know what they say:

“ Good judgment comes from experience, and experience comes from bad judgment.”

Fast-forward to today, and I’m an Android developer with five years of experience. The most vital lesson I’ve learned from my experience is that having the proper architecture is just as important as finishing the job on time.

A day or a year from now, you’ll probably end up in a situation where you can’t maintain the code, you have tight coupling between the modules, or you end up writing the same code over and over again.

An easy solution to all these problems is being cautious while writing the code. It might be obvious, but it’s certainly not easy. Developers have to learn a lot of concepts like:

  • Dependency injection
  • Repository patterns
  • Base components
  • State management

#android #kotlin

How To Set Up a Dependency Injection Framework With Dagger2 in Android
1.05 GEEK