How Long It Takes to Close

Our Policy expects our developers to be fast. The §36 pays for quicker delivery and the §8 penalizes slow movers by resigning them if they don’t close in ten days (at the time of writing). Why ten days, if our tasks are very small and how long does it really take to close an average task? Can we do something to close them sooner?

Why Refusal Is Penalized?

We at Zerocracy, as you know, are strong advocates of freedom and the “No Obligations” principle. You, as a developer, are supposed to work only when you feel like it. If you don’t like the task assigned to you, you simply refuse it. No strings attached. However, Zerocrat will penalize you for such a refusal with a few negative reputation points, according to the §6 of the Policy. Why so? Here is the logic explained.

90 Days

While working under the management of Zerocrat you earn reputation points, according to the §18 of the Policy. Each successful task completion gives you as many points as big is the budget of the task. Say, the budget is 30 minutes. You get +30 points to your reputation when it’s closed. However, the points will fade out in 90 days. Let me explain the logic behind this rule.