3 pitfalls to avoid in order to move ahead in your development career

3 min read
May 20, 2021 9:28:00 AM

3 pitfalls to avoid in order to move ahead in your development career

To successfully complete each task they’re entrusted with, a developer must often be patient and resilient, while also knowing how to assert themselves and be aware of their abilities. Whether he’s a freelancer or an employee, the developer must absolutely know how to express himself to his team, and highlight what’s possible — as well as what’s not. Indeed, clients and managers don’t always realize the scope of the missions and projects underway, as the developer profession can be such a mystery to the uninformed. nexten.io has put together a few points that every developer should consider with one recurring theme: communication’s the key!

Knowing when to say “I don’t know”


When compared to superstars, some developers don’t dare to reveal their lack of knowledge when faced with an assignment, for fear of disappointing or reflecting a negative image on their hard skills to their manager. As a result, they get stuck in a project they might never manage to bring to fruition. Moreover, quotes and deadlines can quickly become obsolete if they’ve been made “by the book.” And that’s where the problem lies: how does one work properly under these conditions? Stress, panic, and impostor syndrome can quickly take hold of you, and everyone knows that carrying out an assignment in this context can be a long downward spiral.

For those of you who do, nexten.io would like to remind you that Rome wasn’t built in a day! It’s perfectly normal not to know all the technologies at your fingertips and to sometimes encounter problems to which you don’t have the answers. This is even truer in the IT world, where developments go very fast! Even the most seasoned developers encounter this problem.

It’s a sign of emotional intelligence to tell your manager or client that you don’t know the answer to their question. Instead of telling them you can’t do the job, tell them you’ve never encountered this issue before and will investigate more on your own. Research on Google, surf forums, and ask for help from colleagues or other developers on the Internet. These are basic best practices that you shouldn’t hesitate to apply on a daily basis.

Knowing how to say “no”


Knowing how to say “no” is a difficult exercise — at work just as much as among friends and family. In reality, when we encounter this difficulty, it’s mostly because we don’t want to disappoint or please. You want to be irreproachable and satisfy your manager and your colleagues at the same time. That seems perfectly normal! Being willing and helpful are certainly qualities that are highly appreciated in a company, but knowing how to manage your time is also an essential quality in the workplace You must remain aware of your abilities and the number of hours you have to dedicate to each project. This shows your manager that you know yourself well, that you can be trusted on a daily basis, and that you’re capable of deploying sustainable actions over time.

Of course, management and human resources might badly perceive a consistent, systematic “no.” You also have to know how to respond critically: without getting angry or frustrated about the situation. In short, knowing how to say “no” means being able to manage your emotions and communicate them in such a way that they are well received by your team. Once again, communication is paramount!

Knowing how to communicate with non-techies


As a developer, you’re faced with one major challenge: very often, the teams do not have the technical skills to understand the development issues of a project. In fact, they’re not aware of the difficulties you encounter, the additional steps that are added to the list, and the difficult deadlines to meet.

It is essential that you take a little time to explain tech projects in progress in clear, simple terms. Remember that “alone we go fast, but with others we go further.” A novice in computer science might bring you some ideas or even solutions you wouldn’t have thought of. For example, a project manager who has an overview of the progress of all the teams could allow you to adopt the necessary distance to understand what customers expect. A department manager, on the other hand, could enlighten you on the market and on the client’s expectations in terms of marketing. To learn more, we invite you to have a look at our article dedicated to this topic: “5 Keys to Explain Your Job to Those Around You.”




No Comments Yet

Let us know what you think