This article was written two years ago and is still out of date. Use the hole I walked in and tell you not to step in it. The following article I will put some points to avoid pits, to share with you. The title is not an exaggeration. That’s what my boss told me at the end.
Programmers are mostly simple, kind people who work with computers every day. I immerse myself in my work and devote myself exclusively to Coding. I am one of these people. Programmer, I have ever seen from several, probably, not skill to discuss basic according to the regulations of the company time to work on Monday to Friday, Saturday and Sunday out hi, world so I want to walk, Saturday and Sunday curtilage in the home to eat chicken, king, attending (I think is good) technology conference, independent work overtime, make things classmate, want to make a performance for the company’s own students. It’s good to take a break once in a while, but the programmer industry is a fast-moving industry, so don’t get comfortable at an early age.
The experience that I receive private life is more rough, it is subcontract mostly, with my docking is 2 packets square. I met the owner who gave money, who paid for subway lunch on Saturday and Sunday. Occasionally, I invited you for several times and cried bitterly. I was too simple at that time, thinking that there would be no problem with friends I knew, so I didn’t sign the contract. For a year, it didn’t work out. Finally, it was a lesson. Below small make up from a few points to tell you where the pit is and how to avoid.
Situations that are not suitable for personal work
Their own reasons
1. Not many skills, and you need help with a lot of things in the company.
2. I have good skills and can do it on my own, but I really don’t have time. It may be family or other things.
3. You work overtime.
Other reasons
1. There is no prototype diagram, and such and such private work, if you do not have finished products can be fixed, basically can not consider, must be a pit. For example, a lot of paid functions, should he test out one by one?
2. Do not sign the contract or the contract is unreasonable, directly calculated.
3. In different places, the other party will not consider us. He considers us, we also do not consider, communication costs are too big.
4. No down payment.
Xiaobian believes that programmer efficiency is more important, of course, some people will say that there is no use writing so fast. Do private work generally still need to have a certain efficiency, of course, not to say write a bunch of bugs, xiaobian does not recommend 3 years of friends to pick up, generally speaking, 3 years of time to learn better, of course, if you have a strong learning ability, can endure hardship (stay up late to do things) energetic circumstances, you can also try.
The contract
Of course I’ve heard of other people taking private jobs without a contract, but the money is there. In fact, based on good faith, even if there is no contract should also give people money, but many people do not consciously. In order not to give yourself trouble, it is better to have a contract, of course, you may also face the possibility of wrangling. The reason for the bickering xiaobian feel that there is no demand and dead, the other enemy is too cunning, take a fancy to programmers do not know how to play. General xiaobian is subcontracted, and at the beginning of the time you and customers must pay attention to talk. We’ll talk about requirements later.
Generally, the down payment is about 15%-20%, which should be mentioned as much as possible. The middle payment is about 50%, and the rest payment is only 30% after half a year of operation and maintenance. My experience is like this, of course, there are some other proportion, depending on how to discuss, no down payment is not to consider, random people say not to do, your time is wasted. A lot of projects may have more than one phase, one phase may do so much, two phases do so much, must be clearly defined which is the current period to do. And it is stated in the contract.
Generally speaking, the contract is in favor of Party A, so we must read it carefully. For unreasonable situations, timely raise and communicate.
offer
Generally speaking, they will give you a prototype diagram, the initial quotation is based on the prototype diagram to report, of course, you also need to and the product or docking person to demand. At this point you can prepare a document and list the big blocks you want to work on. And then you’re given a couple of days to make sure you’re up to it so you can look at the prototype, list the feature points, and make a quote on each one. You need to check in constantly.
Both clients and subcontractors will tell you that the functionality is simple. It’s a whatnot and a whatnot, and you get it done quickly, and this is part of trying to get you to estimate less in terms of price. Just listen and don’t take it seriously. You may end up finding that the person you’re talking to doesn’t understand what they need until you meet the customer.
When you decide to meet, each other began to talk to you the price, actually looking for you before, they had the heart to the price of early expectations, generally avoid can be in accordance with the time and effort, once exceeded expectations may consider the other substitution, but the price is and discuss, you begin to quote a slightly higher price, of course, don’t be too exaggerated.
Haggling is generally unavoidable, this time to take out the quotation sheet you prepared, is not necessary for the above demand, only yes or no, do or do not do. Don’t let them say maybe or maybe, because their maybe or maybe is a big problem for us programmers.
For temporary needs, it is necessary to quote separately and reflect it in the quotation sheet, as well as the workload record sheet, email confirmation or wechat record.
demand
Try to communicate with only one person to avoid too much confusion, but you have to help them out if they are confused, which is sometimes the case. Generally, there are products to connect with you, and generally, they will not let you contact the customer directly. In short, the demand must be closed. If the customer’s demand is not considered clearly, and later remembered what was missing, this should be discussed. (Add money and time)
In fact, the requirements have been almost confirmed in the quotation stage, but the actual situation is that many problems are found by you or the customer in the follow-up work, and they need to be added or changed temporarily. Of course not he said to change the change, we programmers first assess a wave, reasonable demand is not reasonable, time cost and he gave money how much reasonable is not reasonable, not reasonable direct diss. Or you’ll find that because of your momentary weakness, you pit yourself to death.
After each requirement confirmation, you can also send your own work sheet to confirm by email or have wechat chat record, that is, you need to have records and document yourself. At least there’s proof that sometimes you’re not too passive.
There are private jobs are their own wages (according to the time of the discount), must not change to change in the process of doing, big demand changes very affect the delivery time of direct DISS, if not disS, you will find that you have to resist all. Small requirements are not the case that we are wrong to change two or three times, this should be written well in advance.
Avoid generally give time is less, and as a background, you test and consider the situation are to be processed, the database design is very flexible, expansion does not want to see the cost, so that said you to extend the poor, give you a week or two, a background management system an API, and docking, can’t both be extended, as programmers, we don’t embarrassed, We apes don’t accept being exploited.
Private work is generally urgent, and our back-end private work is different from the front end, there is generally an API and a background, of course, do not report too low, of course, too high, you may be passed, most customers have a budget. This is according to our own situation, xiaobian belongs to the more realistic said that we should pay attention to xiaobian a pit through. So make sure you stay away.
Code warehouse
You must submit the code to your own warehouse. You must pay the money first and then the code. You must pay all the money.
If your team is set up for you, talk to them in advance.
Give & Gain
Of course, taking on private work takes time that would otherwise be fun or comfortable. If it is done or similar, it is to improve your efficiency. But if it takes too long, the cost is too poor to match, do not take it. If it affects your normal work, do not take it. Therefore, it is recommended to work for more than 3 years. Generally, this period of time has enabled me to do projects by myself and solve some problems.
After finishing a single, might as well relax yourself, find friends to play, relaxation is also an essential part of progress.
discuss
In fact, xiaobian feel that the most important programmer is learning ability and a solid foundation, of course, finally can have some achievements I believe that those who have a sense of responsibility, reliable people, small victories by wisdom, big victories by Germany. The above are the blogger’s personal opinions and views, welcome to discuss.
The article continues to be updated at ⛽️. Additional blogger arranges + original 150 thousand literal test questions, including 17 special topics. Follow “Java Junior talent show” reply to “Interview” to obtain the Java junior talent show interview notes. PDF
This article is formatted using MDNICE