[Programmer's gossip] developer? Programmer? Coder?

Developers are from Mars, programmers are from Venus, so where are coders from? 

 

No matterCpper,Javaer, OrPhperWait, many developers have experienced the following confusion: I am an engineer (SDE,Or developer),ProgramMember (Programmer), OrCoderWhat about the coders?

This question seems meaningless, or even a boring glossary. However, we use this as the starting point for all topics because there is no absolute right or error in any point of view, what determines the final choice is precisely from the perspective of the problem-identity is of course an important influence. Ass decides the head, so you don't need to repeat the truth.

 

Okay, let's go back to this topic first.

Software Development Engineer (SDE,Or developer) Is the title of most of our software developers. Since it is a profession name, its identity is naturally inseparable from the profession. As a development engineer, his primary responsibility is to develop practical applications within a limited period of time.

This includes at least two points.

First, the development goal. The Development Engineer's development goal is to use, and the program without use value is meaningless;

Second, development costs. Since it is a profession, the work of development engineers is often driven by commercial factors. Its development features are highlighted by a large number of functional requirements and limited costs. Therefore, developers must be able to balance various needs (including time costs.

 

Programmer (Programmer) Is often simply attributed to a group of tech-savvy fanatics who are more driven by interest and develop challenging things. This may not be accurate, but there is no doubt that the name of the programmer gives people more technical sense and ideal colors, so that many people regard him as a title of pride. I also like to boast of being a programmer, or even manyItThe company did not write a line for yearsCodeTechnical Directors also like to boast as programmers.

A notable characteristic of programmer development habits is the pursuit of perfection: The latest method, the smallest binary file size, the least amount of code, the most powerful functions ...... Time? Well, development time is never the deciding factor for programmers to work, and it is not even taken into consideration. execution time is an important factor. All programmers hear this, just like cats smell it.

It seems that software development engineers and programmers are very different. No wonder some people say that software development engineers are from Mars and programmers are from Venus.

 

In addition, some people set a level for the two titles. It seems that after a period of time, programmers can become a software development engineer. Of course, I do not agree that different pursuits lead to different development.

Although we map two completely different actions to the two naming rules, these two actions often appear in the same person at the same time: You may be a development engineer at work, after work, he is more like a programmer. He may treat some problems as a development engineer, and others as a programmer.

Many software projects have a long development cycle. One important reason is that software development engineers have incorporated a lot of personal fun into the development process, and have developed many features that I personally think are cool and unnecessary. A programmer needs to develop satisfactory functions within the scope (cost) of his ability to use software only by himself.

 

Different from the preceding two naming conventions,CoderThe coders are often referred to as blue-collar workers in the software industry "). No one is willing to be such a blue-collar worker, because physical workers in the software industry are almost synonymous with dummies.

In fact, most developers often play the role of coders. Think about your experience of copying a large piece of code, repairing, modifying, and modifying a function, and then copying another large piece of code.Coder? It is impractical to separate these "physical code" fragments from the "mental code" fragments and send them to two developers.

Even ifCoderSuch a profession is only engaged in the "physical strength" work that translates design into code. Their work is still important and worthy of respect. In addition to successful design, the quality of coding is equally indispensable for any successful software project.

If you really lead some commercial project development, you should be deeply aware of the significant impact of coding quality on a project, developers with reassuring coding quality won't be simple coder roles in any organization.

 

Again, whether it isSDE, Programmer, orCoder, I tried to make some definitions not to let you tell from countless developers who belong to which type. On the contrary, I think that for the vast majority of developers, it is not always playing a role, but different roles in different aspects at different times.

We distinguish these types to clarify a role. However, you know that the world is complex, and people are not static.

Related links:

[Programmer's gossip] How long can a function be written?