Case Study: ( As Specimen) We Are Looking To Maintain Funds To Celebrate Programmers/Projects That Use "Micro-Tasks" For Their Development.

3년 전

So we will look into funding as many micro-tasks (programming) i.e issues on GitHub etc (in relation to steem whether open-source or private) as possible in the near future but especially related to developers who are struggling to attain limelight, many of whom are here in the steem ecosystem.

We will like to add "swag" into their game with tiny inspirational gifts (e.g micro-funds etc) to celebrate them and to tell them that they are an important part of the steem ecosystem. This will involve steem witnesses as well. 

The recent methods applied by (in their development), by creating micro-tasks, instead of more complicated tasks, per GitHub issue, has birth something grand. An entire enterprise model that @macrohard will look to carry on with henceforth. 

With micro-tasks (programming) per Github issue, "everyone" enters the paradigm, adding more swag to our enterprise. 

Yes, it is popular to have your "issues" pending for days even months on GitHub or in general because you can't find developers with "time on hand" to work on them, especially with large tasks per issue. 

Yes, when there tasks or issues require a high level of complexity, time, effort etc there are more "barriers to entry" for developers to participate.

This also removes "novice developers" or "amateur developers" from the picture altogether as the tasks are easily beyond their capacity or some of these developers may never feel competent yet enough to consider, approaching or attempting these task reuqests. 

All barriers to entry are removed, with micro-tasks per Github issues.

Here is what we mean (with a recent sample) is an open source project, with its code on Github. is also an open-source project built around steem. 

While has struggled with finding developers to build it into completion, has recently experimented (a different approach) using micro-tasks (issues).

Micro-tasks (issues) refer to task requests that require very pinpoint and simple coding (small tasks). So instead of requesting create a landing page for (using one Github issue); with micro-tasks, "issues" (in relation to building a landing page for ULOGS) can become as simple as: 

  1. "add a picture" to my landing page 
  2. change the wording of the title of my landing page 
  3. Add an outgoing URL into an image on my landing page that says "Click Here" 
  4. Add footers to my landing page.
  5. Change the favicon
  6. Add a feedback button with corresponding URL
  7. etc

Looking at the scenario above, the ULOGS approach instantly removes "all barriers to entry" for developers creating perks for participating developers and project owners alike.

In general, for nice projects, programmers are more ready to help even for free. Some coders love open-source projects enough to want to help you build your code without financial compensation but when the issues involved are large and perhaps complex, it adds a time constraint and other odds to the equation, that may make them "retreat" unless ofcourse, you can pay for their time and bid better than other project owners. etc 

Too, many full-time coders have their own projects, thus, they are likelier to buy out time, if the (programming) tasks in relation to your projects are less-complex and can be completed quickly.

In the last two days, ulogs wrote out 13 issues on Github. Within the first day, it got some 13 programmers who have shown interest. While the first 4 tasks, were already assigned to a certain programmer; the second programmer who was assigned the subsequent 4 or 5 tasks, proactively took it upon himself to do all 13 tasks within the first 24 hours. 

This is testimonially intriguing and is easily birthing a new enterprise as part of what @macrohard will constitute as we start to organize our model. 

Micro-issues are also easier to pay for and negotiate price on than are large tasks. Being easy and snappy, programmers become better receptive to even "a token of appreciation"

Another developer showed testimonies of this (with the scenario involving ULOGS mentioned above), as he was proactive in mentioning that he would be willing to take up some of the tasks on little or no payment. Note that, this particular developer has very limited "time on hand" as he tends to his own projects and large projects of others. 

Another developer was specific about the micro-issue he wanted to take up. He looked at the list of micro-issues and picked one that he was capable of handling. This is testimony indicating that with micro-issues, even amateur developers can participate. They may want to hone their skills in production and will be better opportune to so in the face of many micro-issues as they can pick simple issues to try their skill-set on after which they can create a pull request etc

Ulogs could afford to add a bounty where needed per micro-issue. These amateur developers can already make their first money or so, in steem or SBD, which is very inspiration enroute becoming professionals.

Moreso, micro-tasks manages to unveil many of these talents, regardless of levels and this key for the steem ecosystem as a whole. Steem is a blockchain; the more the developers the better!

@macrohard looks out for all levels of talent (programming), thus, is picking interests in projects that apply the use of micro-issues as micro-funding can also apply there. Too, projects that apply these method, help us with curating "developers" (with all levels of expertise) as we seek to add "swag" especially to the game of developers who are struggling to enter limelight.

Beyond this, as mentioned in the last post, we will look to send out inspiration micro-funds out gradually and maintain resources to make this possible. As we look for projects that apply "micro-issues" for their development, we will able to support both parties, projects and developers alike as we will be able to afford micro-funding. If we are able to give out gifts to developers who apply to micro-issues, then we will also be indirectly helping the development of projects. In general, we look to support projects in general but with inspiration gifts, which can sometimes take the form of micro-funding. Please read our previous blogs for details.

We will not always indicate our efforts as not every gift requires publicity. Basically, we have highlight a projects within this post that has adopted the "micro-issues" method for their development and we will look to curate "developers" who apply themselves to taking up these issues as we seek to inspire selected ones. The whole process of selection is a fun, manual process. Many times, the timeliness of the gift is of pertinence than the gift itself.

Overall, we will maintain a fund and seek just the perfect opportunity proactively, to inspire and celebrate developers, especially developers who struggle to enter limelight. We will also seek to inspire witnesses on steem who fall under this category. In due time, we will expand. 

According to the last post, we will like to start from the Philippines and "Ulogs" came to perfect play within this post as it hails from the Philippines. 

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  trending

Hii I have upvoted you.... please can you upvote me back on my recent post please

Congratulations @macrohard! You have completed some achievement on Steemit and have been rewarded with new badge(s) :

Award for the number of upvotes received

Click on the badge to view your Board of Honor.
If you no longer want to receive notifications, reply to this comment with the word STOP

Do not miss the last post from @steemitboard!

Participate in the SteemitBoard World Cup Contest!
Collect World Cup badges and win free SBD
Support the Gold Sponsors of the contest: @good-karma and @lukestokes

Do you like SteemitBoard's project? Then Vote for its witness and get one more award!