Mycro is a new way to get technology built.
Post a Mycro development task to the board, or submit a solution to other posts.
Each post has an associated, prepaid, financial bounty.
Submit the accepted solution to instantly receive the bounty.
Solutions are viewed on a "first code, first serve" basis - a queue of submissions.
Note: All bounties are held in escrow by us to ensure payment for the developers who submit accepted solutions to development tasks.
At its core, Mycro is a developer-to-developer marketplace
Developers who can develop quality, straight-forward solutions have an advantage over developers who over-architect, and over-design their solutions.
We understand that there are some developers who are not comfortable with the competitive programming world.
However, competing in a competitive programming platform can serve as great training/practice for a passionate developer.
Mycro is merging a new perspective on competitive programming, with a conventional dev-for-hire ecosystem.
Our belief is in decreasing the cost of developing quality technical solutions.
We believe that by developing solutions in a piecewise manner, this reduces the cost of developing an entire solution.
Similar to Kaggle.com, Mycro developers can spend their time developing a solution,
only to have their solution rejected, or have another developer's solution accepted before their own.
Data Scientists on Kaggle are accustom to this.
However, this concept is foreign to developers.
Posting Development Tasks
Sign in, or create a Mycro account. Once you are logged in, you can post a development task to the feed.
This is the Post form you will see when logged in:
Setting your Bounty
You can set your bounty to be whatever price you see fit.
The price of the bounty should be worthwhile to potential developers, but also affordable for the Post Creator.
Post creators must fund the development tasks upon creation. Mycro serves as an escrow for the funds.
Per each task, Mycro charges 15% of the bounty amount.
Mycro places emphasis on development tasks with simple, concrete scopes.
We have created two example posts to help understand how development tasks are posted.
Both example posts are prefixed with "Example #x:", where x is either 1 or 2.
These posts are the only two posts upon which no solution will be accepted.
These two posts are purely for demonstration purposes.
To submit a solution to a post, you must:
You must be logged in
Your account must be Onboarded
All Submissions are in the form of Github Gists.
By using Github Gists, developers who submit solutons can showcase
an arbitrary amount of file containing source code, and Github repositories.
To submit a solution, you can create a small set of files containing the code,
or a single README.md file containing some basic information, with a link to the repository containing
For more information on Github Gists, visit Github Gist
When you want to submit a solution, this is the submission form you will see when logged in:
We use Github Gists for both Posts, and Solution Submissions.
This enables developers to submit a small set of files containing the solution,
or basic information linking to an entire Repository of code.
For simple solutions, we recommend creating a small set of files in your Gist. These files should contain the solution itself.
For more complexed solutions, or for organization, you can also create a single README.md file.
The README.md file can contain a description of your solution, and a link to the repository.
However you choose to organize your solution is up to your descretion.
The Gist link you submit will serve as the official submission. This submission will be reviewed by the Post creator on a "first-come, first-serve" basis.
When viewing your Github Gist, you can simply copy the link of the Gist directly from the Address bar in your browser.
For example, https://gist.github.com/USERNAME/61c4e397d337975f4cd3d72605f1a3f4
For the link to be valid in Mycro, just add the ".json" to the end of the Gist link.
You must be logged in to onboard your account.
Click the onboard button in the navigation bar above.
When logged in, the above menu will show the following options:
Onboarding onto Mycro requires that you have a Stripe account.
If you do not have a Stripe account, you can create a Stripe account through our Onboarding process.
Rewarding Solutions (claiming bounty)
Each post of the feed displays the amount of solutions submitted by developers
Submission count is shown at the top right corner of the post:
Important: Once a Solution is accepted by the creator of the Post, the bounty (minus Mycro's fee) is directly sent to the winning developer.
The creator of the Post can view the solutions submitted by developers by clicking the "submissions" button on the Post.
Each Submission is viewed as a queue - one by one.
When the creator of the Post is ready to review the solutions, the post creator can
select either "accept" or "reject" on the solution.
Important: After a Solution has been accepted, the associated Post will disappear from the feed, as the development task is now marked as complete.
Communicating with the Post Creator or Developer
Since we use Github to host Solutions, and Posts. Developers or Post Creators can use the comment feature on the Gist Post, or the Gist Solution.
If the developer, or Post Creator is using a README.md file to indicate the location of an entire Github Repository,
communication can then be done through foundational Github tools (issues, pull requests, comments, etc).