3 Tricks I am using to become a better developer
I wasn’t always a good Android developer. I struggled quite a bit when I first started. But instead of giving up, I decided to improve by practising a few key principles every day. These principles have not only helped me become a better developer but have also guided me in other areas of life. Whether you’re stuck in your job or navigating your final year in college, these frameworks can be your guide. Feel free to adapt and change them as you see fit.
P for Principles:
- Conversation is the Key
- Comfort Zone is the Enemy
- Understand Problems with the Help of Writing
1. Conversation is the Key
Imagine your boss asking you what kind of impact your code has on the project. How would you respond? If you can’t provide metrics or show any numbers that reflect the value of your work, it might seem like your code doesn’t have much impact. It is where conversations come in.
Talk to Your Seniors: Have regular conversations with your seniors or team leads. Ask them questions like:
— How does my task solve problems on a bigger scale?
— What kind of impact is my task having on the product?
-Maintain a Work Log: Keep a detailed log of the tasks you’re working on. It helps you track your contributions and makes it easier to answer questions about the impact of your work.
When you understand the broader impact of your tasks, you can better convey this to your employer, showing them how your work contributes to the success of the product.
But what if you find that your tasks aren’t making a significant impact? What if they seem redundant? That’s where the next principle comes in.
2. Comfort Zone is the Enemy
If you’re bored with your tasks or they don’t seem to have much impact, it might be time to step out of your comfort zone.
- Ask for Uncomfortable Tasks: Challenge yourself by taking on tasks that are outside your comfort zone. Start with just one or two. These tasks might be more difficult, but they’ll help you grow as a software engineer and allow you to contribute more meaningfully to the project.
Uncomfortable tasks are often where real growth happens. They push you to learn new skills and solve more complex problems. But what if these tasks are too challenging? What if you’re struggling to solve a particularly tough bug? That’s when the third principle comes into play.
3. Understand Problems with the Help of Writing
When you’re facing a complex problem, whether in code or life, it can be overwhelming. The best way to tackle it? Write it down.
- Break Down the Problem: Start by writing the problem down in a notebook. Break it down into smaller, manageable parts.
- Create a Roadmap: Once you’ve broken down the problem, create a simple roadmap that outlines the steps you need to take to solve it.
Writing helps you clarify your thoughts and make complex problems more approachable. It’s a powerful tool that can make even the toughest challenges seem more manageable.
Final Thoughts
These principles have been invaluable in my journey to becoming a better Android developer. By having meaningful conversations, stepping out of my comfort zone, and using writing as a tool to understand problems, I’ve been able to grow both as a developer and as a person. I hope these principles can help you in your journey as well.
If you want to learn more, I have a video for you:
If I’ve made any mistakes in my explanations, please forgive me. I hope you enjoyed reading this and found it helpful.
Thank you,
Your Captain (the Commute)
Hitesh Kohli