What makes a great developer

Article in English 🇬🇧

16 november 2021

One day, in a company I worked, a HR on technical side asked me how I could define “what skills need to have a developer who works with you? 

When you can say that this developer is very good, but that isn’t very good?”

Here are my thoughts about what’s making a good developer:

- Communication (notify about where he is on a ticket, ask relevant questions, provide useful feedback, notify about coming/leaving just for the team to know, humor is a +)

- Meet deadline (does what he said, say what he does)

- Make mistake and learn from it (don’t do twice the same mistake)

- Ease work of others (create reusable components, reuse existing components, make the extra-mile by easing other people’s work)

- Provide with solutions if he gathers problems

- Business-oriented (Be able to do trade-offs when necessary)

- Positive attitude (always warrior, problem-solver and nice to talk with)

- Take responsibility (be able to handle project from A to Z, give ETA, deal with many people involved and complete it)

- Having web standards and simple mental scheme

- Technical (understand implication of BE/FE from his work)

- Eager to learn new things, research new areas, simplify his code

What can be breaking things:

- Not enough communication

- He doesn’t respect guidelines/deadlines

- He’s not saying where he is, notify others of coming/leaving