Coders: Which programmer do you belong?

Aaron is the founder and. Net developer of MarkedUp. In this article, the author lists several representative types of best programmers based on what he sees at work. They have their own characteristics and personalities. in software development, such characteristics and personalities are undoubtedly revealed. (The following is the compilation content)
In daily work, you will surely find many interesting things. What the best programmers do is very interesting. As a matter of fact, the best programmers currently discussed are mainly judged by their judgment, behavior, personal attitude, and incredible ways of working, sometimes these programmers simply pursue the content in the document and are not good at solving problems through analysis.
Almost every software developer is short-circuited. That is to say, the various types of best programmers listed below always belong to you.
1. Pet expert programmer: dedicated technology
This type of programmer encounters a fatal error: Love a technology with only a clock and do not call other technologies. In fact, this is not a commendable advantage. This kind of programmer looks like a programmer who is born to fall in love with this framework. It can be said that the technology he like cannot be put open or lost. Even a person who breaks the casserole and asks the truth in his life.
No matter what the question is, his answer is always irrelevant to his character type:
"Hey, we need to implement a content management system in the Rails framework, but what database should we use ?" Mongo
"Multi-User blog engine ?" Mongo
"Key business consistency system ?" Mongo
"Inventory management system ?" Mongo
"Electronic medical record system ?" Mongo
"Distributed Data Warehouse ?" Mongo
Programmers of the pet expert type will find various reasons in any software development project, regardless of whether these reasons have practical significance. However, once you try to refute his point of view or idea, they are emotionally unacceptable, even if you have a very good relationship with him, it is useless. If he knows that his thoughts are wrong, he will not tell anyone. Instead, he is more willing to secretly use others' correct solutions at the crucial moment of the last second.
2. October programmers: conservicians do not have to repair them.
The goal of an Austrian programmer is to do everything possible to protect the normal operation and integrity of the system, regardless of the cost. In addition, such programmers believe in a very simple philosophy, which is a basic principle that leads them in software development and management practices: as long as they can still be used, you must never fix it.
No matter what kind of software, as long as it is under the protection of the oracle, it has always been the platform, the deployment Program, the database and the operating system that will never change. But you don't have to worry, because the artist will keep staring at these seemingly old components. Maybe he won't win every battle, but he will fight fiercely for every battle.
The past also represents the future in the world view of the Austrian artist. So he will fight with those who want to upgrade his PASCAL code library released in 1981, even with tears.
3. futuristic programmers: catch up with the crowd and pursue cutting-edge technologies
Futuristic programmers can be said to be the opposite of October programmers-today is the future, and any code written using yesterday's development tools is unparalleled in the eyes of futuristic programmers. Their goal is not a philosophy-to pursue the latest and most cutting-edge technologies.
Don't be surprised if you see futuristic programmers blow your nose in front of you and boast that you have seen the latest JavaScript News on Hacker News recently, because they didn't scream in front of you like they did at the Justin Bieber concert, they're taking care of you. Even when Microsoft Research or the Server and Tools Team releases a new product, they seem enthusiastic even if they do not understand the purpose of those products.
However, it should be noted that if you are a futuristic programmer, the positions of DevOps engineers, QA engineers, and Release engineers are natural enemies of futuristic programmers.
4. Information aggregator programmers: Be careful and reluctant to publish code
Information aggregator programmers are very cautious, but they are full of uncertainty about their cautious behaviors. They live in a world of cognitive disorder: they are proud of their work, but do not want to let others know when they need help.
Therefore, the aggregator usually hides the code and does not want to publish the code. Carefully avoid access records, and do not want others to track some of their modifications. His biggest fear is code merging conflicts, because such exposure risks are the biggest.
Maybe a aggregator programmer is happy to tell you how amazing his job is, but it is hard to know his code. In the end, programmers with Information Consortium are doomed to fail. Such actions are not accepted by others, and existence is also of no value. We only hope to make better improvements in the short term.
5. Artist programmers: quality? Beautiful? Not both.
Artist programmers are just the cousins of the consortium and futuristic programmers. Artist programmers tend to build perfect code lines with all their thoughts. In addition, an artist programmer is also an easy-to-use person. The software he creates is the embodiment of his feelings and the vivid embodiment of his individual talents.
Artist programmers will also consider the following question: if I do not add a semicolon in JavaScript, will the statement be more beautiful? Is it more perfect to wrap this block? What they care about most is appearance, followed by quality.
Artist programmers are not the kind of programmers in this industry. They cannot objectively discuss and evaluate their work, nor can they find their position as a colleague.
6. Isolated programmers: code is everything
Island programmers are the most lonely people in the ranks of programmers. Such programmers have a lot of desires for Software creation, but their short board is unwilling to interact with others. The ideal condition for an island programmer is to keep the minimum level of communication with the outside world, and strictly control it at his convenience. His life is just code, no human.
Unfortunately, reality and ideals are often quite different, but these programmers have to go to the company for work to survive, so they are forced to communicate with colleagues or customers, this is indeed a huge burden for them. Therefore, they can only avoid meeting, telephone communication, and email receivers. When they encounter problems, they would rather query over a hundred project documents than ask their teammates.
Just like information integrator programmers, island programmers are doomed to fail. Software development is like a team movement and does not accept alternative rules that do not comply with the rules.
7. agile programmers: quick success, often abandoned halfway
Agile programmers are a utilitarian who strives to improve software efficiency and personal and team productivity. Unfortunately, his understanding of agile philosophy and implementation strategies are rigid and rigid, making people laugh.
The initial intention of agile programmers is very noble: to improve the way software is developed. Such programmers are very vigorous, but there are also disadvantages: any problem that has been discussed for more than four hours will eventually become a bubble; any project made in the final sprint will basically shrink.
In addition, it is worth noting that most agile programmers have a common problem: pretentious. In the process of program development, especially when selecting some small components, stick to your own opinions, resulting in errors in the Network File System or unsatisfactory implementation of the driver program.
8. Illiterate programmers: programmers with simple skills
As the name suggests, illiterate programmers always encounter a lot of trouble when reading others' source code. Sometimes they basically don't understand others' code.
In other words, illiterate programmers and island programmers are like a table brother. They only take the time to understand the basic programming structure for their favorite programming languages and have a full grasp of the programming syntax, but when I see the code written by other programmers, I am completely ignorant. In this case, we call it a "code-blind" programmer.
When other developers ask "Why don't you use our standard interface to generate a conversation", illiterate programmers usually stare at their toes and then muttering to themselves.
The above just lists some of the best programmer cases. Of course, the best doesn't mean that it is not good. As long as you apply this best feature properly, it will become your specialty. I wonder if you are a top programmer?

Original article: pythonontheweb