How to bring an employee to clean water?

Question

Business Informatics

There is a suspicion that one of the team members (distributed) transfers his work to someone else.
How to bring it to clean water?
Responds with a delay, does not make quick fixes, the quality suffers. Sometimes he says that it itself has broken (that is, it simply does not understand what it is about) Does
anyone have any ideas how to get rid of the intermediary? Better yet, go to the one with whom he works and take him to the team

Answer 1

Break some part of the functionality (intentionally), leaving in the source code, where the real performer will get in any case, an "offer" to contact you. No, not explicitly, of course)
A simple "pseudo-code" example:

...
var goToImplementation = 10000;

var hello = IWantToOfferYouAJob(goToImplementation);
...
function IWantToOfferYouAJob(yourPotentialSalary)
{
   if (yourPotentialSalary is enough)
   {
       var writeMeToEmail = "[email protected]";
   }
}

Something in such a style that without understanding the task it would not catch your eye, but with a deeper study, a general picture emerged that the bug was intentional and you were invited somewhere. That is, a real performer may think that your employee is the owner of the project, but the code should give a real picture so that he contacts you directly, and does not unsubscribe to the employee

Answer 2

If the work as a whole suits you, then it makes little sense to change something and look for a real performer. And if you don’t like it, then it doesn’t matter who the real performer is, you need to knock on the head with whom you work with. And to explain that in the code everything is in order, but in organizational matters it is bad.
Well, if you want to find a real artist, then probably the fastest way, something like "You need to go to the site, register, fill out a monstrous plate with some last field in the form of an email to which a confirmation letter will be sent."
Or try to implement a bug with autocomplete :)

Answer 3

Talk and offer to sell the contact before dismissal
Before the conversation, take away all rights

Answer 4

I confess! This I work at night for different people, and in the morning I give the finished code. (It happened in a day or two, depending on your tasks). I'm already with things ...
Come up with a small web service with a REST API that will process the returned result.
The result must change. Break the call function neatly. Ask for a fix.
Any developer will have to connect to check.
All connection requests are always "recorded" for example in the database (IP / UserAgent / ...)
In real time, discuss what the function does incorrectly. Ask for a run for testing and showing. (Find out the IP of the worker and ...)
To be sure, you can break a couple of times. Watch all IP addresses
If there are suspicions that exactly different people: check IP for GEO, ...
then return OFFER for a certain IP, instead of data.
Well, then break it down and refine it ...