Ironically, he is bashing about outsourcing, but he himself is doing just the same. Of course, he does it the clever way (I read the description at teamed.io,

Ironically, he is bashing about outsourcing, but he himself is doing just the same. Of course, he does it the clever way (I read the description at teamed.io, how he makes software-development cheaper by paying "more"): By breaking down the tasks into 30 minutes microtasks, he will only buy the "fat" from the programmers cow. The muscles, filaments and veins, he does not buy. Of course, you can buy only the raw implementation part (at best, only the typing) of a software -- but somebody will have to do the reading of the specs, to do some guesswork ... and so on. By buying micro-tasks, this company does use the fact, that many people will only count the "real" net programming time but not the time in-between those micro-tasks -- reading the specs, preparing the next job, doing the thinking, maybe communicating, waiting for the next assignment ... And the final clever way is: The time estimations come from the company and that is the base for the payment. When a contractor took over a job for 30 minutes and worked on it for 59 minutes (without all the reading and other stuff as said before) ... will he go and reject the money because he nearly worked 100% more on it than expected? Will he really tell the company, that he is not that big talent, he was hired for in the first place?