Why did you say "it's just a code farmer"? We refused.

Why did you say "it's just a code farmer"? We refused.

The root cause is that 90% of the people who say this do not understand technology, do not understand the industry, and think that programming is typing. This includes the following four aspects: not respecting programmers, not just missing one, greatly underestimating investment, but not having to need programmers.

Do not respect programmers

The foundation for working together is mutual respect. In the old saying, "" makes sense and talents need to be respected accordingly, however, many people do not pay attention to this point when sending invitations for "only one programmer is missing.

If you need a programmer, and the title you recruit is really "we have a programmer", then most people will be sprayed after reading the title, the title "codenong" can be used by programmers for self-modesty or self-ridicule, but it is inappropriate to call it a good programmer unless you are familiar with it ), just like in your alma mater, you can repeat it for one thousand times, but you are not allowed to repeat it again. "codenon" means that programmers can claim to be one thousand times, but others cannot repeat it.

A lot of people will say that there is nothing to do with it. We can't afford to joke about it. It's not a good joke. Yes, we like to be lively, but we don't like to play games. The same applies to other industries. For example, "designers" do not like to be called "artists", and "hair styles" do not like to be called "shaving heads.

There is also a more disrespectful behavior-not respecting the talent of a good programmer, manifested in the fact that a good programmer provides a quote based on his rich experience and profound technical skills, when kindly giving suggestions, the demand side will have the following words and deeds: first, because you do not know the technology, you will not seriously consider the suggestions and will say, "That's what you can do, it should be OK ", nor do they tell the team that they understand technology, that is, they are self-disciplined and do not know how to listen;

Second, we will use some cheap comparisons to make a bargain. We will say, "This is not complicated. Is the price a little higher? If it is outsourced to XX, it can be done by a few K. "You should look for it. You need to know that a good programmer can be the top 10 programmers, don't take the price of the Three-stream technology to humiliate people who don't have the first-class technology.

There is also a lot of demand posts, like programmers and technicians looking for lanxiang, think that they are doing well, and that they are doing a lot of work, and that they are always at the core, programmers are tools. In this post, I first boast about what the team has already done, and then I wrote, "because we are both XX or XX professional and do not understand the technology, I am looking for a technical master, it's worse than balabala. The lines between the lines show that you have prepared dumplings, and it's worse than vinegar. In fact, it's already prepared. What about my dumplings?

A technician once helped a team build a website for the Challenge Cup project, and then kicked him out of the team because of the limited number of people who thought he was not the core. But it doesn't mean that there are problems in this way, but most of them are.

Therefore, respect is the first step. Only by respecting programmers can you respect your needs.

More than one missing

Many posts have such words as "just" and "one", but I carefully analyzed them. My mother-in-law, where is a soldier, it's just a group.

Most people think that programmers should be full-stack and even all-powerful. I don't know why a project should be divided into front-end and back-end, and why I need to make APIs. Such a project accounts for a small proportion of people, most people in the past ), the conventional thinking is "What you see is what you get". websites and apps are designed to put these images in code. That programmer should be able to do it quickly.

Someone once needed an APP and found a programmer to do it, but he really thought that he was a programmer, but he didn't have any other interface design or interaction design, but the project was simple, the programmer agreed, so he spent one night drawing an interactive design drawing for him. As a result, he always thought it was just like that, and he still doubted the level of people.

However, due to the popularity of the Internet, more people know the frontend and backend and some basic development things, but still think that "because of the simplicity of your project, so it is enough to find another programmer. "or" this won't be okay. You should learn it very quickly. "Their projects are actually ambitious from a technical point of view, architects, analysts, developers, testers, O & M personnel, and other teams are required. However, they think that they need a program. At least the project looks like it is not complicated.

After all, there are a lot of things that are not so real about Internet products. Building a building, how tall the building is, how much it really feels, however, people who are not familiar with Internet products do not know the complexity of information interaction and the overall architecture. The BOSS who built the building will not be stupid enough to say "I am just two moves away ".

Therefore, before releasing the demand, ask a technical expert to help evaluate the talents needed. I don't know what kind of talents I need.

Greatly underestimating Investment

"It will take two months ?! Just a few pages !", "As long as you do well, the price is not a problem. You can talk about it from 10 thousand "... For example, we have experienced or heard a lot better. Many people who say "we are just a programmer" want to find a good technology and develop it quickly. Is it better to pay a little labor fee.

This is a problem that the authors of most of these posts often make an underestimating investment. The investment here includes time and compensation.

In fact, it really depends on the demand side's requirements for the project. If you really want to do anything, go to pig Bajie network, go to weike.com, and go there, and grab several hundred projects, thanks to pig Bajie and Wei Ke, haha.

However, most of them require better living, and the price should be "reasonable ". An outsourcing team provides the following quotations:

A wants to find someone to make A website, with A budget of 1 w to 3 w, B quote 3 w, promise 40 days, C offer 5 k, promise 30 days, then I made A quotation for D for 1 k and promised 50 days. Result A found D.
B: 3 w is just to attract you. No 10 w of such projects can be done at all.
C: 5 k is reasonable. When I get the money, I will download some templates for you and modify them.
D think: I can earn 1 k, download a template, and then it's over.

But what afterwards?

What kind of things do you want to make? What kind of price do you have to pay? "just a coders" won't let you buy 50 LV for 50 yuan, but you will only buy the artificial leather with the LV logo.

Before programmers are needed

When your project reaches the point where programmers are needed, will it be "poor programmers?

Some projects that recruit programmers say "everything is ready now and development is poor". However, looking at some well-prepared projects, we will find that only idea, documentation, no data, and no thinking, there is no actual research data, and it is all the brains that have been shot, and the flow of water.

Is your idea really effective? What problems have been solved? Do users like it? Is the market large enough? Can there be a business model? Is it technically possible? What are the core advantages? How high is the ceiling? How are competing products developing now ?...

I haven't figured it out yet. What do you say? "If a programmer develops, the technical partner is worse? Reliable projects will attract reliable programmers.

Small suggestion

Demand side:

Understand respect, understand the progress of current projects, do a good job before technology implementation, and suggest that you do not want to show yourself how you want to recruit people like you do, then, we will give reasonable time and compensation to our talents. How can we reduce the cost of small business and how can we enlarge the long-term benefits of large business.

For programmers:

Not all "just one coders" are looking for a spray. After all, 10% is really bad, however, 90% of the students who "just sent a code farmer" are busy. They are purely ridiculed. Even if they are paid enough, they cannot do anything. Therefore, they can improve their technology, avoid yourself from being the 90%, and then teach the 90% students who are "just a programmer" how to do things, you know.