Working on someone else’s code

[rakibhasanbd4723]

Conclusion can be frustrating, but before you start to curse it, try to understand why the code is written in such a way. At first glance, something can seem completely unreadable but diving into it can help you to understand the code and save you from the future trouble.

I can not say that working with bulgaria phone number legacy code is trivial. Of course, it is much nicer to work with Android Jetpack, write the entire code in Kotlin, with no need to support very old Android System versions. But – in my opinion – what doesn’t kill you makes you stronger.

I have learned a lot about the Android Framework and Support Libraries. What is more, I had an excellent environment and play-ground to apply mechanisms from the “Working Effectively With Legacy Code” book.

If you have faced similar issues and have some advice, please leave a comment.

Related posts
How to Provide Accessibility in Your Native Android App with Jetpack Compose | Part 2: Scaling • Text Size • Focus Order • Labeling
The Low-Code Guide That Every Business Owner Should Read
How to Provide Accessibility in your Android App | Part 3: Semantic Properties and Screen Orientation
How to Provide Accessibility in Your Native Android App with Jetpack Compose | Part 1
SSL Certificate Pinning in Flutte