Soft Skills Every Developer Should Have
A few weeks ago, I interviewed someone who wants to become a developer. He was concerned that he wasn't good enough technically and that he will never be. "What makes a great developer, in your opinion?" he asked me. I answered briefly: "A great developer must have technical skills, it's undeniable. But what really makes you great are your soft skills".
This answer surprised him. And it may surprise some of you. But I insist: soft skills are important, more important than technical skills. Because once you get the right soft skills, technical skills come naturally. Let's see which skills and why.
- Be curious. Always learn new things. Learning publicly is even better.
- Be patient and perseverant. Hard work always pays off.
- Be creative and proactive. Take the lead of topics and keep the big picture in mind.
- Be egoless. Don't make fun of others. Accept criticisms with kindness.
- Know how to communicate. Listen to others and learn how to be understood.
- Help others. You'll be more trustworthy.
- Be organized. Don't be late. Know what to do and when to do it.
📚 Curiosity and continuous learning
Let's start with curiosity. That one is important since it will open new gates for you. Being curious means being willing to learn continuously and discovering new things. Never stop asking why things behave the way they do or what's going on under the hood. And when you learn, be sure to do it publicly, even if you can be wrong. It'll bring many opportunities to you.
💪 Patience and perseverance
You surely have heard that perseverance is the key to success and this is especially true in development. We can quickly get demotivated by the amount of work or things to learn. There will be times when you'll feel like you won't progress anymore, when you spend hours on that silly bug, when you'll think you need to stop that side-project. But, you need to be patient and perseverant. Hang in there. You'll gain more and more experience as you learn and build new stuff. Hard work always pays off.
(I'm not saying you should spend all your time coding. Breaks are important too 🌴)
💡 Creativity and proactivity
In the end, solving problems and finding new ways to look at things is the core of our business. So it's crucial for us to find new solutions and look at things differently, to have another perspective on how things work. By improving products, creating new libraries, or making things faster, we face new challenges and better solve problems. And who knows, you could create the next big thing.
Finding such solutions require you to be proactive. Don't be passive and wait for work. Take the lead of particular topics. It's usually appreciated. However, it's important to always keep the big picture in mind. You should know what the trade-offs are to these solutions and where you're going.
As an example, you could suggest creating an open-source library as part of your project. This would raise awareness around your project (or company) in the open-source world. Thus, you would be seen as proactive and accountable. One warning, though, it's not because you've taken the lead of a subject that you necessarily need to over-defend it.
Raise your hand if you ever met that person who is too much pride of his code, makes fun of others, and doesn't accept any critics. ✋
It's not because you don't know something that it means you're incompetent. It's not because you have a question that it means you know nothing. It's not because someone else knows fewer things than you that it means you're superior to that person. Take a look at this list of things Dan Abramov didn't know in last December. Does it make him a bad developer? I don't think so. You can be a successful developer and not know many topics as long as you have a domain of expertise and the right attitude.
You need to be humble, accept criticisms positively. If one gives you legit feedback on your work, don't take it as an offense. Learn from it and get better. If you're working in a team, introduce pair-programming and code reviews, you'll gain a lot from it, provided you know how to communicate...
It's the most challenging and important skill to get, in my opinion. It's easy not to understand each other. On the one hand, what we say can differ from what we think or what we wanted the other to understand. On the other hand, the other person can understand something different from what he wanted to hear and what he actually hears.
Furthermore, a vast majority of people don't like listening to others. They just pretend they're listening and prefer to talk about their stories, what they think or what they've done.
However, as a developer, you can't behave that way. You'll work with other developers but also with product owners or managers. So you'll have to explain clearly why you disagree about that technical choice. You'll also need to explain to non-technical people why setting up reminders and push notifications are not just "if statements".
I noticed a recurring pattern when developers are onboarded on a new project. Some of them usually start with a refactoring, which makes sense because it's a good way to ship something and learn how things work. However, the refactoring process turns out to be a rewriting of the original code in another coding style. The code is neither more performant nor more readable. And this kind of "refactoring" usually goes along with a bunch of remarks like "What the f***?" , "But who wrote that?", "Oh, we need to use that framework.", "I don't understand anything, that code is s***".
Of course, a new look at the code is a great opportunity to make it evolve, but do it in a smart way. Kindly provide feedback. Be empathetic and be comprehensive. Put yourself in the shoes of the previous/current developers. Maybe they had to deal with deadlines, maybe they didn't have the time to modify this legacy code or maybe they didn't have the knowledge you have right now. There are plenty of reasons why one can write awful code.
When you can empathize, you can feel what others could feel. You already think of what they could think and what they could face. Thus, it makes you more trustworthy since we know you are that kind of person. And it makes you a better communicator since you think about the expectations of your audience. The same goes for your app users.
👨🏫 Helpfulness and mentoring
I'm sure you know someone to whom you never ask for help because you know it'll be annoying for him. How do you feel in these kinds of situations? I feel stuck in these moments. Coding is hard. We encounter bugs every day, and it's normal to reach out for help. So, be helpful. Take time with other team developers to help them with their tasks. Help people on Stack Overflow, write technical posts, be there for others.
It's also a great idea to mentor someone when you have the knowledge. Not only do you gain a deeper understanding of what you teach at that time, but you also offer the opportunity for another person to grow. Be careful though, helping others can be time-consuming.
Would you give a task to someone unreliable? Constantly late? Overwhelmed? I bet you wouldn't, and that's totally understandable. Well, you don't want to be that person. It's essential to be trustworthy. If you do your tasks in time, it means one can trust you and give you more responsibilities. But doing your tasks in time means being organized. For that, you can use to-do apps such as Todoist.
However, you should know when to say no to something. And that's where communication is important. If you think you'll lose your time in that meeting where you won't even talk anyway, say it and make sure you are being understood. As an example, don't say "That meeting is useless. I've got other things to do.". You'll be seen as aggressive and overwhelmed. Instead, explain yourself and be opened to the discussion: "I have the feeling my presence isn't necessary to that meeting, and I would like to fix that bug by the end of the morning. What do you think?".
Getting all these soft skills deeply change the way you work. Once you get curious about a topic and get a continuous learner's mindset, you understand how things work, and you get more experience because you actually care about learning. Be creative and proactive, don't just wait for work. Take the lead. Sure, tasks can be daunting, and the amount of work can demotivate you, but you need to be perseverant to succeed.
A developer usually works in a team, so it's important to be egoless: accept criticisms, always seek feedback and learn from your mistakes instead of rejecting them. You also need to know how to communicate with others. Be empathetic, understand others' point of view, truly discuss things. Whenever you can, help people and teach things, give workshops, tips, write articles even if you're not an expert. Working in a team implies that you expect things from your colleagues and we expect things from you, so be organized.