DEV Community

Cover image for 10/10 Habits to Become a Better Software Engineer
Muhammad Usman
Muhammad Usman

Posted on

10/10 Habits to Become a Better Software Engineer

They get increasingly more niche. But they're not what you think.

1. Teach, teach, teach

To master something you must teach it. Explaining concepts solidifies your own understanding. Become the expert you wish you had. If you can't explain it simply, you don't actually know it yet. So teach it anyway, even before you feel ready.

2. Build a solid T foundation

Go really deep on a single framework. Then diversify. Depth first, breadth second. Pick one and go all the way down before you spread yourself across ten others.

3. Use the rubber duck technique when you're stuck

Talk it out. Articulate your problem as if it was speaking to another person. 99% of the time you'll figure it out. You don't even need someone listening. Just say it out loud and the gaps in your own logic start showing up.

4. Ship early and ship often

Embrace the imperfect. Stop waiting for the perfect. Launch your v1, get feedback, iterate. That's how you grow fast. Perfect doesn't teach you anything. Feedback does.

5. Code review your own code

Seriously. Be your toughest critic on the code that you write. Read your own diff before anyone else does. Catch the lazy shortcuts yourself first.

6. Documentation, documentation, documentation

Write documentation as much as you can to help your future self. You will forget why you made that decision. Write it down now, while you still remember.

7. Automate the mundane

If it's a repetitive task, script it. Set up CI/CD. Work smarter, not harder. Anything you type more than twice, automate.

8. Embrace every single time you have available

Whether it's during work, on your lunch break, or before work. Time is no excuse. Fifteen minutes here and there adds up faster than you think.

9. Seek constructive feedback, always

This will help you fight imposter syndrome. Actively ask for feedback. That will only help you grow faster. Don't wait for a review cycle. Just ask.

10. Learn from the best

Even if it's open-source projects, your team leads, or your senior devs. Read what people write. Their code, their commits, their comments. All of it teaches you something.


Did you learn something good today as a developer?
Then show some love.
© Muhammad Usman
Don’t forget to subscribe to Developer’s Journey to show your support.
Developer's Journey

Top comments (0)