krow
May 17th, 2005
ideas, portfolio, projects, softwarekrow: a distributed software development engine
build custom software from loose specifications, using a large pool of developers and a market to determine priority and compensation. Abstract:
Software developers, potentially geographically-scattered, execute abstract project visions, earning and circulating virtual currency (hereafter ‘krowmids’) which translates into respect, ownership, and real money for successful projects.
The project owner specifies their vision, naming problems to be solved and designing tests which will pass when the system realizes the owner’s vision. Trusted developers enumerate use cases, clarify tests, architect solutions, and segment the project into subprojects, which become concrete [probably automated] tests and tasks to be implemented by those same developers. Developers, customers, and investors pledge krowmids to their favorite projects and subprojects; the implementor earns those pledged krowmids, less any krowmids they pledge to delegated tasks.
Earned krowmids result directly in project ownership, which translates semiannually into more krowmids as those projects are licensed and used by both internal and external customers. Project owners set the prices of libraries and applications, though a mechanism for determining alternative payment structures would be beneficial. External modules may be used by krow projects, contagiously incorporating them into the system.
Senior developers train junior developers in technical skills, project management, and specific projects, granting incremental authority [with a competition-derived belt system] to decide implementation details. Developers strive to earn quantifiable respect and honor from the system and their peers, concurrent with economic sustenance.
krow manages the project database, developer and customer interfaces, project and developer accounts, source control, and test sandboxes. For these services, krow taxes the exchange of krowmids to dollars and vice versa. Transactions on internal markets should remain frictionless.
Thus project owners provide developers with tangible incentive to organize and realize their vision. Developers enjoy merit- and result- based compensation in a relatively stable system, contributing to a wide variety of projects. Investors and customers enjoy finer control over project and feature priorities, while the system enjoys converting the desires of investors, customers, and developers alike into an efficient market for technical labor.
Stumble it!Comments
Leave a Reply
