7 types of developers today: which one you belong to?

Currently, computers in general and programming, in particular, have a lot of ways to learn and learn knowledge. Depending on how you approach programming and your own efforts, your destination will be very different.
We have listed 7 typical developers in the current working environment. You try to find out who you are, and want to be one of them?

Recyclable ticks:
The characteristic of this type of developer is that they will do whatever it takes to get the job done with their experience and skills, even if they are limited.
For example, a developer like this will accomplish the task by "picking up" open source software or other (free) support tools. His most valuable asset is his willingness to learn, to study what is needed to get the job done and the ability to "absorb" knowledge. His resourcefulness is also often very high to be able to work with anything that can be used for work.
It sounds good, but not every customer will like it. For customers with limited knowledge, they will praise and accept their products. But the fact is that he uses the built-in tools to create a "new-looking" product for the customer, but he doesn't really develop the whole thing. As of today, what this developer brings is not very impressive.
If you are a front-end developer, a responsive website with pure CSS will definitely be more impressive than a similar product using Bootstrap or W3CSS, right?
The old man has experienced:
This type of developer is certainly not the rebel type in this dynamic and innovative industry, but what he brings is also valuable: huge amount of knowledge and experience.
He seems to be an outdated man, incapable of using new tools and technologies, but as an experienced scholar, he understands the fundamentals of software development. He may not be the fastest or understand the new technology, but like the story of a turtle racing to win the rabbit, he always brings the same value as he does from start to finish.
This type of developer is proof of the existence of previous generation code styles - that they still exist and are still valid. He may not be the one who made the drastic changes but maybe based on many difficult situations when the debugging story returns to the basics.
Heavy enthusiasts:
The workaholic is not enough to describe this type of developer, but programming is his way of life. Developers of this type often work on expectations from their superiors or customers and of course take pride in their products.
This fanatic often spends his lunch break working, perhaps completing projects before deadlines, even working overtime or at home. In rare spare moments (which they allow themselves), he reads books, newspapers, and documents to develop his skills. Of course, with a major interest in software development, he's an introvert, and the code world seems to be the place where he feels most comfortable secure. The code makes him satisfied but never makes him depressed. Of course, with such capabilities, this type of developer is more suited to the role of a “worker bee” than a queen bee.
The bookworm knows all:
All-in-one nerd is simply a mobile encyclopedia. He could spend hours passionately discussing the history of a programming language or analyzing imperfect code that worked.
It can be said that, in the programming world, he is like a poet who sees code as an art that needs respect and analysis. Every statement block with him must be executed perfectly, only standards, with clear principles, while requiring only secondary time. He also set high standards for himself, so the main problem of this type of developer is: what can be done in a few hours could cost him months.
Must correct, is he is not incapable. The problem is that he creates his own work, by creating new tools, libraries or even reinventing the new system, to fit his own standards. He wants to bring his "works of art" to the pinnacle of standards.
It's good to have an all-knowing nerd on your team, but you need to make sure to give him the most important small details, rather than giving him a whole piece and making his perfectionism The project is delayed monthly.
Ninja developer
Just like a Ninja, this type of developer is less talkative and more mindful. These Ninja developers are quite similar to heavy enthusiasts, but they have more life than code and code.
For his teammates, he can be a difficult puzzle. Imagine, he can do every task quickly and flawlessly. But he shows you the results, not the reason why he can do them. He is quiet but still works well with the team.
Never discouraged, he solved all matters quickly, no matter how difficult the location time. His ability is so cold that he chills your spine, and makes you constantly wonder why he can do it. He does not express the attitude or opinion of the task assigned but only focuses on solving it, so working with this type of developer is a really comfortable and great effect.
You can find this kind of developer at the start-up company, or the start-up team. Everything is going great if you working with this Developer.
And if you are a big fan of one of the most potential start-up in current coupon industry CouponUpto where they offer many deal, coupon for many service from Javascript to Python, you can find that their project is growing so fast and their code is always fresh and clear.
Goodwill ambassador:
As the name implies, the goodwill ambassador is the face of the team. He is frank and unofficial as well as the PM (project manager) of the team. He does not directly code, but has a deep understanding of the software development process or project workflow and such.
He has leadership skills as well as proactive communication with customers. This allows him the ability to please both aggressive customers as well as rebel developers in the team. In his position, he ensures that every project meets customer requirements and satisfies them, acting as a bridge in the communication between the customer and the development team.
In such a "fragile" position, goodwill ambassadors often feel the need to be rewarded, even though he doesn't have to do heavy work (like code). For the developer in general, he is a role model. members of the advertising program, perfectly appearing in front of the camera and trying to sell products, while the team behind the scenes (stylists, make-ups) do the same difficult work and still receive a small amount of money. more.
Anyway, in a time of market economy, he is an indispensable factor for the development of a dev team, and what he receives is, in fact, well worth what he did.
Two-hand cowboy two guns:
This is the type of developer you often find freelancing or outsourcing. "Two-armed two-gun" works faster than most people with the ability to take many jobs in many projects at once, but the cost is the quality of the code: he often overlooks a few parts of the development process. software. He felt that optimizing and re-checking the code took too much time. His lines of code are often chaotic because he often disobeys best practices (or "best practices") or even OOP (object-oriented programming).
But miraculously, even though his code looks like a fair, the product works as expected. He seems to be a testament to the famous saying in the dev world: "If it looks stupid but it works, then it is not stupid". This is not a good thing for long-term project development, but in difficult situations, this is the type of person who can save your project.
However, like the word a doctor prescribes, his code will be hard to read, not to think about fixing or developing. If an error is caused by a collision of code in subsequent developments, updating his code is almost as hard as rewriting completely. Obviously, you cannot debug things you don't understand or even read.
Of course, the 7 typical developers we listed above are for reference only. You may find yourself one of them, or you may find yourself similar in some ways, but the important thing is, we hope you can see your own strengths and weaknesses. to be able to reach your desired developer model.
Do you also want to be a strong talented ninja?