In the IT world , programmers are hard-working, stay up all night to write code, and spend half a day around a bug. Even more tragically, Rice University , the mad science department of the Pentagon, recently announced that the US Department of Defense plans to invest tens of millions of dollars to develop tools that can help computers automatically write code. If the research and development is successful, a large number of programmers will lose their jobs, even if it is just a bowl of "youth rice".
Despite this, it seems that it cannot stop everyone from applying for computer science or joining the passion of the IT industry. There are more and more programmers who are influenced by an idea at work or in life and start to learn programming and become "halfway monks". Programmers from professional classes are no longer the mainstream, and the definitions between occupations are no longer so clear.
In my coding journey and programming experience, I have encountered many strange adversaries, and even more strange allies. I've found at least 5 types of code warriors, some are great comrades, others seem to mess with every plan I have.
But they all have a place in the pantheon of software development. Without a good mix of different programming styles, you may find that your project is either too long, too unstable or too perfect for no one to do it.
Programmer style
please take your seat!
In Beijing, and even in the whole of China, as far as our IT industry is concerned, programmers can be said to be of all kinds, and they can only sigh with emotion: The forest is getting bigger... The following 5 different types of programmers, which one are you?
1. The duct tape programmer
The code may not be pretty, but damnit, it works! The code may not be pretty, but it works!
This guy is the cornerstone of the company. When there is a problem with the code, he can quickly fix the leak and never repeat it. Of course he doesn't care about how the code looks, how easy it is to use, and other trivial issues, but he can get it done without a bunch of crap or babble. The best way to use this kind of programmer is, after you point out the problem, just walk away.
2. The OCD perfectionist programmer
You want to do what to my code? What do you want to do with my code?
These guys don't care about your deadlines or your budget, which are nothing compared to the art of programming. When you finally receive the final product, you have no choice but to heartily admire that beautifully formatted code, no, flawless code. That code is so efficient, you don't have to do anything with it, or you're just superfluous and blasphemous. He is the only one qualified to change the code.
3. The anti-programming programmer
I'm a programmer, damnit. I don't write code. I'm a programmer , rub! I don't write code.
There is only one simple truth in his world: writing code is bad. If you have to write something, you are doing it wrong. Because someone has already done it, just bring it. Even if the time he spends writing code and other programmersAlmost, or longer, he will tell you how fast this development practice is. When you get the project he submitted, maybe the actual code is only 20 lines, and it's easy to read. The code may not be fast, efficient, or forward compatible, but the effort is minimal.
4. The half-assed programmer
What do you want? It works doesn't it? What do you want? Does the code work?
This kind of guy pays little attention to code quality, that's someone else's job. He only completes assigned tasks quickly. You may not like his code, and other programmers hate it, but management and customers love it. While he will cause you a lot of pain in the future, he can single-handedly meet the deadline, so you can't laugh at him (no matter how much you think).
5. The theoretical programmer
Well, that's a possibility, but in practice this might be a better alternative.
This guy is more interested in extras than what he should be doing. He spends 80% of his time staring at the computer, 15% complaining about unreasonable deadlines, 4% figuring out an affair, and 1% writing code. When you get his final product, you always see things like, "I could have done better in this place if I had more time."
Which one are you?
Personally, I consider myself a perfectionist. So, what type are you? Or what kind of hybrid? Or do you think there are other types not mentioned above? Please leave a message in the comments
Every programmer has a different personality and different abilities. Because of this, different programmers have been derived. Some programmers compare themselves to coders, while others consider themselves experts. So what kind of programmer are you, come and see ^_^!
The four common types of programmers
1. Artisan
This is a very different group of programmers. Other programmers are more concerned about the technology itself, but such programmers are more concerned about the results of implementation. For these programmers, the product created by the technology is the focus, not the technology itself.
So it's hard to define them in terms of front-end, back-end, DBA, security engineers who are willing to learn any technology in order to create a great product, some just taste it, some are very proficient because of need or interest. They usually have a rebellious spirit, instinctively resist authority, like to challenge leaders in a certain field, and have a hacker spirit in the traditional sense. They are extremely strict with themselves and others, have a strong desire for control, and like to intervene in product-related things other than programming, such as design, UI, marketing, etc.; because they do not want to reduce the product due to a mistake in a certain link. influence, although they are not always right.
These programmers love to program, but programming is only part of their lives. Other parts of their lives will be traveling, farming, painting, playing music, playing kendo, and playing the flute. These hobbies are completely inconsistent with the programmer temperament in everyone's eyes. These programmers are also workaholics, stubborn, and mavericks.
Because of all these, it is difficult for craftsmen to work together in ordinary enterprises, they always feel that their talents are limited, and the people around them cannot keep up with his rhythm; they are in a sense the unstable factors of the company, or It is an angel or a devil; most companies do not need craftsmen, but for great or aspired companies, craftsmen are more important than experts. Experts can make existing products industry-leading, but craftsmen can create new products. products thus changing the rules of the game. Because a business suitable for artisans is so minimal, some of them choose to start one themselves.
2. Code Farmer
At first, there was no such word on the Internet. The origin of this word was because of a programmer's self-deprecation. In fact, the code farmer is also the main implementer of the software. Like thousands of migrant workers, they are just the creators of the software building. Maybe they are familiar or proficient in several languages, developing existing frameworks.
They are blue-collar programmers and do some physical work, but this is not a bad thing. Someone has to do things, and the freedom of programming gives coders a lot of room for creativity and learning. If you admit that you are a coder and enjoy what you do, that's a very beautiful thing, but the problem is that many people are not willing to be coder themselves, but are forced to become coder, they should be musicians, Athletes or businessmen can become code farmers for various reasons, doing what they think is boring and repetitive physical work, so they are not happy. In this state, they are exhausted physically and mentally, that is, they are most likely to send programmers to eat youth meals. , After the age of 30, it is useless to write programs, and you should switch to management and other stupid things.
But when they do become managers, usually, only a very small number of people find what they like to do, and most of the other coders will continue to complain. To sum up, code farmers are the largest group of programmers, and they have the highest plasticity. There are middle school students who have just learned programming, graduates who have just started working, and senior engineers who are still willing to fight on the front line after working for many years; Code farmers, first of all, they must admit their identity, and then find their own interests and directions, or be willing to be code farmers for a lifetime, or prepare to switch to the other three types of programmers, or change industries to pursue their original dreams.
3. Expert
In the software industry, these experts have struggled for many years. They are proficient and knowledgeable in one or more areas. Within a company, these experts are often referred to as senior programmers, CTOs, or architects. After they have designed the structure of the software building, they usually arrange for coders to do it, and then write the core code themselves.
They are experienced and technologically forward-looking, able to plan ahead and react to the decaying trends of the software edifice and technological changes in the industry. They are simple-minded, like their jobs, and pay well. They keep up with the times by reading the papers of scientists. The software industry is very special. For the manufacturing industry, the difference between the results brought by the outstanding and the mediocre is usually only one to two times.
Therefore, experts are the treasures of the company, and any company must spare no effort to win or cultivate experts; at the same time, becoming an expert is usually the ultimate dream of many coders. So if you are an expert, please accept my high regards.
4. (Computer) Scientist
They are not so much programmers as they are mathematicians. They invented all kinds of theories, algorithms, and terminology, and the lengthy proofs and calculations in the textbooks came from them, and other programmers benefited more or less from their results. Sometimes one of their papers can change the mindset of an entire industry, but they usually don't and don't like to commercialize that shocking theory. In contrast, they prefer to be immersed in the ivory tower of science, enjoying themselves and being happy.
They are the least frequent programmers among programmers. There are even some masters who have never written programs in their entire lives. You may think that this violates our definition of programmers at the beginning, but who said that programming has to use a keyboard?
Two different types of programmers
There are two extreme archetypes of programmers—the "Zen programmer," who we call the stagnant programmer, and the "programmer who can't control distractions," which we call the restless programmer. Both are pretty extreme, so they should be on opposite ends of Bell's bell curve, right?
wrong. In fact, moody programmers are incredibly common.
The effect of pictures is more useful than words, so I now use pictures to illustrate the state of the mental world of two programmers.
Programmer with a heart
What would a programmer with a heart like water do?
He writes code. It's the only thing he does, and that says it all. Perhaps the more important question is what he's not doing: he's not being affected by distractions. Focused attention, focused revision, focused coding. One to two hours of pure code time, followed by a 20-30 minute break, usually away from the computer. After that he will continue to start writing code. (The time mentioned above is just an example. He can schedule his time in other ways - but he always balances and manages long-term productivity.)
His thoughts flowed slowly like calm water. Of course it's not like that kind of permanent frozen ice.
This is what the mental world of a programmer with a calm mind looks like:
Unsettled Programmer
Even if your mental world looks like a stagnant programmer right now, as long as you open Facebook or check your email or whatever while compiling.
After a few minutes it will look like this:
Ladies and gentlemen, this is what happens when you check your email and open Facebook. If you also have a bunch of real-time notifications, instant messengers, and checking your RSS feeds and Twitter, the result is a brain-shattering disaster like the picture above.
You may not have fully recovered from this picture. It can happen at any time, not on a particular day. Even if you minimize all the useless things in the spiritual world to the taskbar, it will still stay there, constantly tempting you and draining your spiritual resources. Friend, time just goes by and you'll be confused how it's gone.
By the way, if you're a moody person, you can still check out the webcomics on our site! Don't have to come back right away to finish reading this article. Don't forget to subscribe to that manga feed! After watching all the manga you can share it with your friends and chat! It's not too distracting to do these things, really!
The difference between a restless programmer and a restless programmer
Programmers who are at ease are more inclined towards long-term happiness and productivity. He has the ability to have high concentration and focus on the target.
The moody programmer is more prone to short-term gratification, which in the long run does not reach his full potential and is both physically and mentally damaging to himself. He couldn't settle down to concentrate.
In fact, whether they are experts or code farmers, programmers serve the boss and the company. Some people say that the income of programmers is very high. Although this sentence is true, how many people see the hard work of programmers. In many large companies, it is always the programmers who work overtime until the latest.