Voluntary certification of programmers in the Work service

 

After communicating with a number of clients, I was greatly surprised by their complaints about the programmers of the "Jobs" service, including those at the very top of the rating. Complaints are not just about the programmers' unwillingness to help and suggest something, which is forgivable, but about their professionalism. Any negative rating they easily flush out by cheating rating by creating a job with another login directly for themselves. So here is the idea of a voluntary certification of programmers who provide services on this service.

What will it give?

- The programmer can show the client a certificate here on the site which confirms that he was tested by Meta Quotes programmers and can do the job properly.

- If the programmer does not have a certificate, the rating will be easily inflated.

- The customers will be able to choose the programmer not by the cheated rating, and on the presence of the certificate.

Suggestions:

- A certificate can be obtained by ordering a certification of oneself, possibly for a fee. In the case of failure the certification can be passed again in 2-4 weeks again for this fee.

- In addition to the certificate for the completed tasks in the certification the programmer can receive a grade. Suppose the programmer is given 3 tasks and each of them is rated on the quality of work, including several criteria. The average grade for each criterion goes into the certificate.

- The verification must be hidden by Meta Quotes workers who will post the verification orders in the Jobs service and then distribute them to those who ordered the evaluation. The programmer will learn that it was a certification only after the completion of work and, of course, will not receive money for it.

- The rating of the programmers who passed certification will be shown separately above the rating of those who have not passed it, while the programmer will not be removed from the bottom list and can be displayed in both lists.

- To write in a programmer's profile the number of lost arbitrations in a prominent place, this information should be displayed when a customer tries to select a programmer. As for example, when sending money through WMID to WMID that has complaints in Black List.

- In case the programmer has lost 2 arbitrations in a quarter his certificate is nullified, attestation is necessary to pass anew. *Quarter between the first and second arbitration.

These proposals are intended to "clean up" the ranks of "programmers" from unprofessionals or inexperienced workers who do the job as if, knock down the price of the work just to get the order and leave a negative impression of the service from customers.

 
MrGold166:


It's very complicated . Having a certificate does not guarantee bad attitudes and disadvantages in the future. Over time, things will quickly go back to normal. The certificate will be a tick.

But the main thing is that in any area no one removes the risks from the customer. The client must choose the contractor wisely.

 

About arbitration, it's a bit of a misunderstanding. There may not necessarily be a misunderstanding on the part of the programmer, there may be a really controversial issue and you need a third party who simply says so-and-so. There was such a thing, but we managed without arbitration.

The rest is all right.

Having a certificate does not guarantee a bad mood or anything like that, but at least it guarantees the absence of fatal flaws (I've seen it).

 
Personally, I don't understand what one can write for the amounts that are announced in the "Jobs" service
 
Integer:

About arbitration, it's a bit of a misunderstanding. There may not necessarily be a misunderstanding on the part of the programmer, there may be a really controversial issue and you need a third party who simply says so-and-so. There was such a thing, but we managed without arbitration.

The rest is all right.

Having a certificate does not guarantee a bad mood or anything like that, but at least it guarantees the absence of fatal flaws (I've seen it).

The first question is always how it will be circumvented. Let's call HIM a lousy programmer. What prevents him on the stage of certification to get together and slowly honestly and qualitatively perform work from three , four declared nicknames.

He will get a few certificates and all will go as before. Then there will be a system of monitoring and re-certification, etc. Everything will drown in control.

 
Mischek:

The first question is always how will they get around. Let's call HIM a crappy programmer. What will prevent him at the stage of certification to get together and take his time to honestly and qualitatively perform the work of three, four declared nicknames.

He will get a few certificates and everything will go as before. Then there will be a system of monitoring and re-attestation, etc. Everything will drown in control.

Not necessarily just a test in the form of a questionnaire with variants of answers. A task and then see if the important points are taken into account.
 
I remember the issue has already been discussed (certification of programmers). There was a lot of discussion, but as far as I remember there was no result.
 
Integer:
Not necessarily just a test in the form of a multiple-choice questionnaire. A task and then see if the important points are addressed.

That's probably why almost all programmers with Job in CodeBase have 0.

 
Integer:
Not necessarily just a test in the form of a questionnaire with answer options. A task, and then look whether the important points are being paid attention to.

This will probably only protect against outright hackers. Should we raise the amount? From 1,000 cues and up. The thugs, realizing they won't get it back, will bail. They won't be able to get away with just one nickname.

It will filter down concretely. And the choice between certified and unqualified will be left to the client.

 

At the moment most of the arbitrations are related to the lack of the TOR. The client gives a vague description or does not attach it at all at the time of signing the agreement, and then they start to find out that they meant this and not that.

In some cases the client's complaints are as follows: "nothing works, check it yourself, I do not need to understand the details of testing" and so on. In many cases the Arbitrator's intervention helps the parties to get on with the claim and complete the work themselves.

 
Mischek:

This will probably only protect against outright hackers. Should we raise the amount? From 1,000 cues and up. The thugs, realizing they won't get it back, will bail. They won't be able to get away with one nickname.

There will be a filtering process. And the choice between certified and non-certified will remain with the client.

It's too much. Still, certification should check the level of knowledge and skills, not the material level. Assessment will not raise prices significantly, prices should be consistent with the capabilities of buyers, otherwise the services will be out of demand.

Reason: