4 things that hinder a developer’s growth

Photo credit: gmast3r / 123RF

The internet is full of tips and tricks on how to become a rock star developer. But in reality, the line between an average developer and a great one is very thin. And technical expertise isn’t enough to take a developer from average to great.

Here are four serious mistakes (arranged from the least obvious to the most obvious mistakes) made by inexperienced developers that inhibit their growth. These errors are so obvious that it’s often hard to identify them as such, even by well-coordinated and experienced teams.

4. Always choosing custom over ready-made solutions

When we face a sizeable creative task, we’re often tempted to build a specific functionality from scratch. That’s what brings us the most satisfaction.

However, before jumping on the custom-solution bandwagon, it’s worth taking a moment and reflecting whether we really need it. Is it really a good idea to spend money on building a custom functionality that doesn’t bring users any value?

Don’t also forget about the future costs that come with maintaining that custom functionality. On the other hand, you’ve got free open source solutions maintained by communities of passionate developers.

If you want to provide users with a specific functionality, consider your current budget and future plans for product development before going for a custom solution.

3. Forcing new technologies at all cost

Technology trends come and go—so quickly that most of us find it increasingly difficult to keep up with the many different directions the industry takes today. Everyone is asking themselves questions like: Should I choose a native language such as Java, Swift, or React Native for my next mobile project? Should I go for Progressive Web Apps instead?

So, how can we judge which trends are short-lived and which ones stand a chance to disrupt our industry?

Even experienced developers are tempted to ride the wave of recent trends. What they often do is quickly master such technologies and then try to implement them in the first commercial project they get their hands on. When expanding the technological stack of a project, they’re surely led by good intentions. They want to make sure that the product develops according to new industry standards.

But when they fail to consider the long-term consequences of their technology choice or its direct business value, implementing new technologies at all cost can become problematic.

Naturally, developers who actively follow the sector developments and gain new skills are among the smartest of the bunch. But when they fail to consider the long-term consequences of their technology choice or its direct business value, implementing new technologies at all cost can become problematic.

Sometimes, developers suggest a hot technology just because they want to learn it, and they seek an opportunity for doing so. Sticking to personal goals instead of the company’s business objectives puts the project in danger.

Team knowledge of new technologies (or lack thereof) acts as a buffer here because it reminds everyone that forcing new solutions can be extremely costly, especially if the developer initiating its implementation leaves the project later on.

2. Estimating undefined tasks

1. Not communicating errors

So, what does it take for a developer to become more than average?