Android app development: fixing bugs before creating them

I wanted to be a programmer when I first saw a computer 25 years ago. Then it was old computers running MS-DOS and the recently released Windows 95. Unfortunately, fate decreed that after university I did not work as a programmer, as I wanted. However, I always dreamed of becoming a programmer, and as a result, I became one.

I became involved in android development, because I was struck and still is struck by the number of people who use devices with this operating system. I also like the fact that you see the result of your work every day and can show it to your family and friends. You can open the app and say, " Look! I did it!"

I try to constantly expand my horizons of android development and around it. Every day I read documents, articles, books. I was involved in the internal accelerator to understand how everything works on the outside. I follow the principle: either I don't take the job, but if I take it, I will finish it, no matter what it takes. I really appreciate the good relations in the team.

There is own app on GooglePlay

Skills/Interests: java, kotlin, junit, android sdk, git, sqlite, design patterns, material design, rxJava, retrofit, mvp, mvvm, mvi, moxy, dependency injection, dagger, jni, firebase, room, android jetpack, SOLID, compose