3 ms·

There seems to be a disconnect on the points we're arguing here. Task scheduling and routing is (almost) the easy part or at least a pretty solvable equation -

There seems to be a disconnect on the points we're arguing here. Task scheduling and routing is (almost) the easy part or at least a pretty solvable equation - there's a whole range of operations and queue theory texts that can make a quick go of managing that. I'm more concerned with the human element. HR overhead, people making sure tasks are getting done well and in a timely manner. "but she doesn't deal with them like they were IP packets, does she?" - No she (he actually ;-) can't they're people.

barry-cotter 15y ago
"I'm more concerned with the human element. HR overhead, people making sure tasks are getting done well and in a timely manner. "but she doesn't deal with them like they were IP packets, does she?" - No she (he actually ;-) can't they're people." That's the point of Exec and of every we-can-disintermediate-this-or-make-it-massively-easier-by-using-IT-and-CS startup. They can treat people like IP packets. At some stage they'll have practically open hiring and most people will wash out fairly quickly but the ones who either excel or consistently fail to fuck up will just keep on getting tasks from Exec, the others won't.