In today’s world, you move backward if you don’t move forward as a developer. The tech space evolves at such a rapid pace that you need to grow and evolve constantly. That can be challenging. It is the #1 challenge for many developers. What helps tremendously is carefully choosing the environment you work in. If you are part of a team that understands this challenge, you are halfway there. A team acknowledging that the status quo isn’t an option will create an environment that promotes your growth and supports your evolution, making reaching your goals much less daunting. Knowledge-sharing sessions, attending conferences, pair programming, or organizing local meetups can make a difference. Avoid teams that don’t embrace this mindset. If you notice that your team underperforms consistently, cares little about code quality, or isn’t investing in a long-term vision of the project or product, then it may be time to look for other opportunities. Spending too much time in an environment that doesn’t serve your goals can be demotivating and even problematic in the long run. Being a developer is more than writing code. You need to build a set of skills that supports you in writing code. You need to be a great communicator. You need to take ownership of your work. You may need to lead. It is no longer sufficient just to write code, especially if you want to stand out in your next job interview. That may be overwhelming, but it shouldn’t be. Start simple and start small. Write down what frustrates you in your day-to-day work and take action. That can mean updating the project’s README to make onboarding new team members easier or rethinking the release train of the project. Involve others to increase momentum, and before you know it, you have made a significant change that benefits you and your team.
@_bartjacobs Thanks for sharing. Apart from writing quality code what other skills a developer needs improve?
@_bartjacobs Love this. A team I was on once used to ask weekly “What is painful for us? What do we not look forward to doing in our process or our codebase? How can we make it better?” And that mindset of constant improvement really stuck with me