8 Types of need programmers, I do not know which one you belong to? _ Other Comprehensive

There are certainly a lot of interesting things to be found in daily work, and it's interesting that the best programmers do. In fact, the best programmers are now talking about judging from their judgment, behavior, personal attitudes, and bizarre ways of working, and sometimes these programmers simply pursue the content of the document rather than use analytical methods to solve the problem.

Almost every software developer will have a brain short-circuit phenomenon, that is, the following list of the various types of best programmers, there is always a one belongs to you.

1. Favorite programmers: The love of the collection in a technology

The fatal mistake that this type of programmer encounters is that it loves only one technology and does not call on other technologies. In fact, this is not a merit of praise. Because this programmer looks like "Born to fall in love with this framework programmer", for their favorite technology can be said to be put off, lost. Even in life is a broken pot to ask the end of the people.

No matter what the problem is, his answer always has nothing to do with his character type:

"Hey, we need to implement a content management system in the rails framework, but which database should we use?" "--mongo database" multiuser blog? What about the "--mongo database" critical business consistency system? "--mongo Database" Inventory management system? "--mongo database" electronic medical records system? "--mongo database" distributed Data Warehouse? The--mongo database

A favorite programmer can find all sorts of reasons for any software development project, regardless of whether the reasons are practical. However, once you try to refute his or her ideas, they are emotionally unacceptable, even if you have a particularly good relationship with him. If he knew his thoughts were wrong, he would not tell any of them, but would prefer to secretly use the correct scheme of others at the critical moment of the last second.

2. Potters programmers: Conservatives, not to be repaired without a last resort.

The goal of the Potters programmer is paramount: Regardless of cost, do everything possible to protect the system's normal operation and system integrity. In addition, such programmers embrace a very simple philosophy, this simple philosophy is to lead them in the software development and management practice of a basic principle: as long as you can use, not to be repaired.

No matter what kind of software, as long as it is under the protection of the arcane, it is always using that platform, the deployment program, the database and that will never change the operating system. But you don't have to worry, because the craftsman will always stare at these seemingly old components, maybe he can not win every battle, but he will fight for every battle and fierce.

In the Craftsman's world view, the past also represents the future. So he will fight with those who want to upgrade his 1981 Pascal code base, even in tears.

3. Future programmers: Rush-tide people, the pursuit of cutting-edge technology

Futuristic programmers can be said to be the antithesis of arcane programmers-today is the future, and any code written with yesterday's development tools looks like an unmatched aversion in the future pie. Their goal is not a philosophy--the pursuit of the latest cutting-edge technology.

If you see a futuristic programmer with snot in front of you bragging about the latest news about JavaScript on Hacker News, don't be surprised because they don't seem to be in Justin's Bieber in front of you at the concert. Even when a new product is released at Microsoft or the Server and Tools team, even if they do not understand the purpose of the product, they are enthusiastic.

However, the caveat is that if you are a futuristic programmer, then DevOps engineers, QA engineers, and release engineers are the natural predators of future programmers.

4. Information hoarding programmer: cautious, unwilling to publish code

The information-hoarding programmer is a cautious person, but it is fraught with uncertainty about its own cautious behavior. They live in a world of cognitive dissonance: proud of their work, but unwilling to let others know when they need help.

So hoarders usually hide the code and don't want to advertise it. Careful to avoid access to records, but also do not want others to follow him to make some changes in the record. His greatest fear is to encounter code merge conflicts, because the exposure risk is the greatest.

Maybe a hoarders programmer would be happy to tell you how great his job is, but if you want to know his code it's going to be hard. In the end, the information hoarding programmer is doomed to failure, such behavior is not accepted by others, there is no value. I only hope that there will be a better improvement in the short term.

5. Artist-type programmer: Quality? > Beautiful? Do not have both

Artist programmers are simply the cousins of hoarders and futuristic programmers, and artist programmers pour all their thoughts into building perfect lines of code. In addition, the artist-type programmer is also an emotional person-the software he creates is the outpouring of his feelings and the vivid embodiment of his personal talents.

The artist-type programmer will also consider the question: if I use JavaScript without semicolons, is it more beautiful on the statement? Would it be more perfect to wrap this piece together? What they care most about is beauty, then quality.

Artist-type programmers are not the kind of programmers the industry advocates, they can't objectively discuss their work, or position themselves among co-workers.

6. Island Programmer: The character is withdrawn, the code is everything

The island programmer is the most lonely person in the whole programmer's ranks, such programmers have a lot of desire in software creation, but their short board is unwilling to associate with people. The ideal working condition for an island programmer is to communicate with the outside world best to keep it at a minimum, and to strictly control it at his convenience. His life is just code, no human.

Unfortunately, the reality and ideals are often very different, but these programmers have to survive to go to the company to seek work, so forced to communicate with colleagues or customers, it is indeed a huge burden to them. So they can only avoid-avoiding meetings, avoiding telephone conversations, shutting down mail receivers, and so on. When they encounter a problem, they prefer to query the hundreds project documentation rather than ask their teammates.

Like information-hoarding programmers, island programmers are doomed to fail. Software development is like a team sport that does not accept the alternative of not complying with the rules.

7. Agile programmers: Quick success, often halfway

Agile programmers are a utilitarian, committed to the need to improve software efficiency, as well as individual and team productivity. But unfortunately, his understanding of the "agile" philosophy and the implementation of the strategy is really inflexible and rigid, can not help but make people laugh.

The initial intentions of agile programmers are noble: improving the Way software is developed. Such programmers do things in a more vigorous and resolute way, but there are drawbacks: any discussion over four hours will eventually turn into a bubble, and any project done in the final sprint will basically shrink.

It's also worth noting that most agile programmers have a common problem: pretentious. In the process of program development, especially in the selection of small components, adhere to their views, resulting in Network file system error or the driver implementation effect is not ideal.

8. Illiterate programmers: Beginners of programming, basic skills and shallow

As the name implies, illiterate programmers in the reading of other people's source code will always encounter a lot of trouble, sometimes basically do not understand other people's code.

In other words, illiterate programmers and island programmers, like cousins, spend time in their favorite programming language to understand the basic programming structure and master the programming syntax, but it's completely Greek to see the code written by other programmers. In this case, we call it the "Code-blind" programmer.

When faced with other developers asking "Why don't you use our standard interface to generate a conversation," illiterate programmers usually stare at their toes and then mutter to themselves.

The above is just a part of the type of the best programmer case, of course, the best does not mean that the good, as long as the best features of a reasonable application, it will become your expertise. Don't know if you are a need programmer?