Many programmers are interested in taking part-time jobs. After all, for programmers, taking orders is definitely a decent and well-paid side job. So, what are the precautions in the process of receiving an order? This article will definitely help you!
1. Choose a reliable platform
There are many ways for programmers to receive orders, but the mainstream is divided into platform orders and private orders. If you are not a bigwig or have strong connections, then taking orders through the platform must be the best choice.
The advantages for programmers to accept orders on the platform are:
①Money is supervised by the platform, which reduces the risk of the boss "running away with money";
②There are a wide range of resources on the platform, and programmers only need to filter, instead of looking for a needle in a haystack Look for potential opportunities to receive orders;
③ There are many types to choose from, and you can find a private job that suits you.
Programmer Inn, WWR, Code City, and devnors are all good choices. The feedback speed, order quantity, and platform reputation on Programmer Inn are not bad. WWR and devnors are more for foreign part-time jobs, while Code Market is It can be used as a supplement to the programmer's inn.
2. Don’t look for a needle in a haystack, but target it
Taking orders is a physical and mental work. Don't overestimate your energy. It's best to select 2-3 orders that suit you, and actively communicate with the boss until the boss confirms the order. Don't worry if you don't find the right one, it's better to lack than to abuse. If you exaggerate your ability, you will not be able to deliver on time in the end, and the loss will outweigh the gain.
3. Do not accept without a deposit
The more mainstream payment method for programmers to receive orders is the 442 charging method.
That is to say, 40% of the project payment (deposit) will be collected at the beginning, 40% of the project payment will be collected in the middle term, and 20% of the project payment will be collected at the time of delivery.
4. Do not give all the codes before receiving the final payment
It is necessary to be defensive. Before receiving the final payment, do not give out all the codes to prevent some Party A from "running away with the money". Of course, at this time, a reliable platform can still recover losses for programmers. Accepting orders is risky, so don’t think too kindly about people~ Before
completing the project, you must communicate the project completion standards and payment time to meet the project’s deadlines. After the standard requirements, Party A will pay the final payment, and both parties are guaranteed.
5. It is best to write the requirements document first and make the final confirmation
Many programmers are receiving orders for the first time, but there are also many small companies that are issuing outsourcing requirements for the first time, so both parties may not be familiar with the order receiving process, and the most likely to leave a big hole is the early demand communication.
If there is no written record and confirmation, it may eventually cause repeated revisions and delays on both sides. Therefore, the requirements document must be detailed, confirm the implementation of each function, and make a final confirmation with Party A. This is the most important step for programmers to take orders, none of them.
6. Communicate the progress with the boss in stages
Confirm the DDL and the first acceptance time, the final acceptance time, communicate with the boss in a timely manner during the completion of the project, and confirm with the boss when completing a large functional module, and optimize some details to make the communication between the two parties as possible Costs and error rates are minimized.
Communication is very important, let the boss know your progress, and put forward some optimization directions when you see your "semi-finished product", so that you will not make a wrong step, and finally overturn and redo everything.
While reducing your own workload, you are also reducing your boss's workload. Our goal is a win-win situation!
7. Be mentally prepared to work overtime
Regardless of the size of the project, receiving an order is an "8 hours away" job after all. So don't think about taking orders when you are busy at work, it is easy to be empty-handed. Don't take urgent orders or orders with unclear requirements. This will infinitely prolong your working hours and work progress, resulting in failure to deliver work on time, and the gains outweigh the losses.
It is best to be able to complete the project in your spare time, and have an account with your boss and yourself.
8. Cherish your reputation
In fact, taking orders is not only a temporary job, but may also bring you a permanent job. If you have a good cooperation with Party A, then he may come to you next time, and even introduce more bosses to you. This is a huge profit.
Conversely, if you treat the project very perfunctorily, even if it is finally delivered and paid for the project, it may ruin your reputation and unintentionally reduce your income a lot.
When programmers take orders, don't make one-off deals.
9. The construction period should be reserved
Don't delay delivery until the last moment, after all, there is a certain risk in accepting orders. Projects generally have some temporary plans and unexpected requirements. At this time, it is necessary to reserve some spare construction time and give yourself some time for modification and optimization.
This is responsible for yourself, but also responsible for the boss.
10. Keep chat history and source code
In order to prevent problems such as after-sales rights protection, you must keep relevant chat records and source codes. Once there are some subsequent battles, you can submit evidence to protect your rights and interests. If you have verbal communication with Party A, you must confirm in writing again to prevent being cheated.
The above are the precautions for programmers to receive orders. If it is useful, don’t forget to like and collect~