For companies to get started, someone must visit Subspace’s website, create a profile, and post a project. Companies can be as involved or uninvolved as they like: they can either rely on their own engineering team to break projects up into tasks for freelancers, or allow expert freelancers to manage the project for them. Either way, the company’s own developers can participate in the project, committing code, voting, and discussing with the community.
There are several advantages to the Subspace model:
Companies access a global talent pool and new frameworks and languages
Companies can scale resources up and down
Companies don’t pay for full-time headcount they don’t need
How payments work in Subspace
Freelance coders are paid out when the project passes milestones. They’re paid in accordance with how much value they contributed, and that doesn't just mean writing code. Coders earn payments for anything that advances the project, including upvoting code that’s eventually accepted, downvoting code that’s eventually rejected, and participating in discussions.
How voting works in Subspace
When contributors commit code, everyone on the project has the opportunity to vote on and discuss it. Code that reaches its approval threshold is accepted into the code base. Coders each earn reputation based on how they advance the code with their commits, votes, and comments, and the more reputation they have in a particular domain, such as Ruby, the more weight their votes hold. Over time, the most skilled and believable individuals exert the most influence and are paid the most.
How does reputation work in subspace?
Developers in Subspace earn persistent reputation scores based on their involvement in projects. They earn reputation for committing code that’s accepted, upvoting code that’s accepted, downvoting code that’s rejected, participating actively in discussions, and responding quickly to other contributors. They lose reputation for committing code that’s rejected, for upvoting for code that’s rejected, downvoting code that’s accepting, and for not participating in discussions.
Companies can supplement their existing engineering department, temporarily scale headcount to hit deadlines, or outsource the majority of their engineering needs. For example:
Supplement: The engineering team at a large enterprise uses freelancers to eliminate technical debt. They host pieces of their code base and thousands of developers audit it, catching bugs and recommending improvements.
Temporarily scale headcount: A startup engineering team uses freelancers to temporarily scale headcount and hit a deadline. The VP of engineering realizes that they’re far behind schedule and releases a large portion of the development budget so thousands of developers swarm-build and test the feature by launch day.
Full outsource: A company needs to build an iOS app from scratch. The company posts wireframes from its designers and the community builds the app from scratch. The company checks in at milestones.
Why do companies use subspace?
There are six primary reasons companies use Subspace:
Build software fast
Never miss a deadline
Pay by outcome, not hour
Plug skill gaps
Identify top talent
Retire technical debt
Why do developers use subspace?
There are six reasons developers use Subspace:
Learn more about Subspace.