Being self-organised is a key attribute for becoming a senior software engineer. Part of self-organisation is the ability to prioritise tasks.

Developers may get stuck pursuing minor software improvements over adding real value. This could be due to inexperience in estimating effort versus value, and not realising when a task is taking longer than expected. Alternatively, the developer could be choosing a low-value task that feels comfortable; achieving a solo contribution.

When you have the freedom to choose what to work on, consider the priorities for the team and how you can best help. Remember: today’s priority may not be the same as yesterday’s, so you may need to shelve what you are working on. This is okay: the work is not lost.

If you are not sure what the priorities are, ask! This will show initiative and higher-level thinking.

It’s important to note that low business value does not mean low value: maintaining a healthy codebase is important. This is where the skill of prioritisation comes in: technical debt reduction must be balanced alongside the goals of the business.

Think: What is the goal? How do I help us get there?