How not to get burned again when choosing a team?

Question

Work organization

Hello. I am developing a project, there is a good technical specification, there is a good front-end developer, there is a cool designer and design, but there are no back-end developers.
For 2 weeks they fed me with all sorts of things, then they do it, they do it, but in fact the daily reports have to be beaten out by force, I looked at the git - very little was done, in general, interrupted work with them. Although they are said to be handsome on UpWorke, there are reviews on LinkedIn, although on the sites that I went from the reviews - something doesn’t work. Their whole team, how they position themselves.
Tell me how to find normal specialists on yii2 or laravel? Who know how to quickly crash in libraries on github, who write work reports that work in general. Or how best to control them?
I only consider remote employees.

Answer 1

Unfortunately, finding a good developer is really not easy.
And a good remote developer is generally a separate "fruit" that matures over the years.
To find such a person, you need to have a good understanding of motivation and know where to look:
As a rule, remote developers are people with a good technical background and good English (they work in international teams).
This, in a sense, raises the bar for salary (the first fact).
As for Upwork, it's very hard to find a real developer here. Upwork does not filter the level of such specialists in any way. And I must admit, it is not particularly effective in combating various levels of fraud, such as: cheating reviews, fake identity, etc.
About 80 percent there (the figure is just out of my head, please don't take it to heart) - these are low-skilled workers (or intermediaries) with problems in self-motivation. This is neither good nor bad - this is a fact (number two), because it is really difficult to motivate yourself remotely, especially if you do not like your job (unfortunately now more and more "random" people get into IT because of hype and money).
Fact number three - most good developers get great pleasure from creating new things, solving complex problems, and interacting with technology (the more advanced the better). Therefore, all you can do in terms of control is to set limits on the conditions of the task and just not interfere (this is me about daily reports).
However, controlling the budget and deadlines is very important, and it is a task from the discipline of project management.
Developers, as a rule, do not do this (and if they do, they are experienced and will ask for more $$ for it).
Therefore, in order to control the progress of the project, you (or your project manager) need to develop (or take existing ones) an appropriate methodology (for example , Scrum ). It is not necessary to copy 1v1, just take what you need, depending on the project and the size of the team.
For example, break the progress of work into iterations (2 weeks long). In each iteration, take some time to decompose and evaluate tasks. Try to get a visible and workable result at the end of each iteration before proceeding to the next one (roughly speaking, the reporting period is every two weeks).
Use tools for collaborative project work - Trello, Jira, etc.
In general, a lot of emphasis should be placed on psychology and establishing trusting relationships with developers, because intellectual work is very dependent on these things (and also on money, of course).
Of course, this does not mean that those who openly put the bolt on the job need to be persuaded and persuaded to work. In this case, it's just not your "passengers".
Well, I recommend looking not on free freelance exchanges by keywords, but on specialized sites: thematic parties (chats / forums on technologies / frameworks), specialized exchanges with selection of personnel (such as Toptal), resources dedicated to work (such as Djinni.co) .
I would also recommend doing some simple selection/testing of candidates yourself, especially if the candidates are from freelance exchanges and not top profiles.

Answer 2

and here is an opinion from a novice freelancer on upwork: I have more than ten years of web development experience in serious companies, fluent English, work experience both on the part of the customer and on the part of the contractor, a completely transparent and real profile that is easy to check, and I decided do charity work and help people solve their web problems professionally and cheaply, but:

• no one cares about real experience
  
• customers on upwork are only interested in the number of projects you completed on upwork
  

Answer 3

Draw up a contract, create requirements for quality and deadlines, fine in case of non-fulfillment, encourage good work, bad tears will merge, you will have to look for good ones, but with such conditions it will be easier for you and them.

Answer 4

Do
not be afraid to get burned and sort through the commands until the desired one is found . Do short iterations of 1-3-7 days; demand
a workable solution at each iteration ;

Answer 5

https://ru.wikipedia.org/wiki/%D0%91%D0%B0%D0%B9%D...