Why do programmers often fail to finish a project?

Question

Work organization

There are many programmers on this site, and for sure, many of them have and had such projects that they undertook to do, but did not finish due to certain reasons. Projects, here, I mean - not my own, but the customer's.
I have this problem from time to time. For example, a month ago I agreed with a programmer on a project to install a new layout on the site while maintaining the current functionality, which he had to do in a week. As a result, the project was handed over in a month, and a bunch of bugs remained, some he did, some very important ones he didn’t finish. Now you just have to look for another contractor
. So it’s not the first time that you first communicate with a programmer before starting work, he seems like a super-pro, and then, some excuses, extension of deadlines and so on. Or they just don't answer.
Here, my goal is not to complain, but to figure out why this is happening, and to establish work so that this does not happen again. Of course, I understand that one of the ways out is to study programming on your own in order to understand how adequate the performer is. But what other methods are there to ensure that the project is executed accurately and without bugs that another will do.

Answer 1

Two main reasons:
1. It's a hell of a job for programmers right now. Therefore, there are also plenty of opportunities to slip away for big money to another project.
2. Estimating project time in programming is very difficult in advance. Almost impossible (read Brooks' Mythical Man-Month, this problem was recognized almost half a century ago, but still has not been completely overcome, and even beginners have been trying for years to learn how to properly evaluate projects). As you work on the project, you realize that you are wasting your time for a penny.
Therefore:
The realization that you are wasting your time for pennies, when there are a lot of projects around - makes you merge.
There is one more problem - it would not occur to you to offer a taxi driver to move your furniture when a truck is needed for this? You don’t hire a Kamaz or a Gazelle truck to take you home from a cafe after a drunken party, but you turn to a taxi driver? It's just a different class of cars and everyone understands that.
With programming, everything is not so - the most difficult task can be offered to a student. A 1C specialist may be offered to make a website. Etc. They confuse admins and programmers, etc.
At the same time, no one refuses the opportunity to improve their qualifications in a new field. And the fact that the performer is not effective in an area unfamiliar to him leads to the aggravation of point 2.
I - no, I'm not quitting. Since I can explain to the customer that the project will cost many times more than originally agreed.
But some people to whom I gave work - merged on the sly, it was like that. The reason was problem 2 and their shyness in explaining problem 1 (that the budget needs to be revised). It is easier for many to merge, it breaks them to go into a conversation and explain everything.
It also happens that a programmer, without saying a word to you, becomes busy for a month or two (another project), plays for time with a "sick hamster", etc. And then he comes back and finishes your project.
I have this problem from time to time. For example, a month ago I agreed with a programmer on a project to install a new layout on the site while maintaining the current functionality, which he had to do in a week. As a result, the project was handed over in a month, and a bunch of bugs remained, some he did, some very important ones he didn’t finish. Now I just have to look for another artist
In the low price segment - this is a common situation.
Normal specialists do not allow such jambs. Although 1 week can easily turn into 2.
There is another feature of freelancing - you are not the only customer with him. He will not refuse new orders, since you, too, can merge and he will remain on the beans. Therefore, the freelancer takes all interesting orders, no matter how busy he is at the moment.
To become his chief, you must give large orders for more than one month, and without interruptions, stably. Or offer a price obviously higher than the market.
Often they underestimate the price and terms either by mistake (it is very difficult to estimate them accurately if we are not talking about a primitive project) or by mistake
Or consciously in order to take an order, kill competitors, and then issue an additional invoice.
1. Move to another price segment. Stop working with the cheapest specialists. Good specialists do not allow such jambs. But their price is not 10% higher. And 2-3-4 times. I'm serious.
2. Switch to work with a flexible payment system (regularly review the terms and cost, divide the project into small parts).
3. Or even switch to an hourly work (there are programs that take screenshots and show what the employee was doing and you can check that you are not being deceived).
4. Monitor the result, for example, once every 2 days.

Answer 2

The reason is obvious - the person is not fully interested and motivated to work with you. Perhaps the reason is that you pay little, there are other more paid orders.
The solution is simple - draw up a TOR, sign an agreement (include TOR in it) and not make more than 30% prepayment until the end of the work. Checked and paid.

Answer 3

Psychologically, this is um ... alas, it is logical.
The programmer means the same freelancer? It is very difficult for a freelancer to refuse orders - they may no longer apply. Therefore, the programmer must deal with your order as quickly as possible in order to start the next one - the quality suffers, non-obvious problems can take 80% of the time - and it becomes more efficient to abandon the project - the programmer does not need the project itself - he needs money for it.

Answer 4

I agree with the first comment about motivation. Most likely your employee is not motivated. But it is also worth paying attention to such an aspect as control. How often do you monitor the work of your employee (for example, what he did today, and so on). It is necessary that these are not empty words, for example, I made a form and inserted a picture there, but for the result to be on the face - this very form with a picture.
It is also possible that the problem is that the employee did not fully understand your idea. In this case, it is necessary to agree that if problems of this kind arise, it is necessary to meet and discuss the problem that has arisen.
It is also worth noting that if you hire a freelancer or a simple worker, look at his portfolio, ask around for reviews of other people for whom he worked. This will help you see the level of your employee and his attitude towards working with past customers.