Proceedings of the 27th Annual ACM Symposium on User Interface Software and Technology 2014
DOI: 10.1145/2642918.2647349
|View full text |Cite
|
Sign up to set email alerts
|

Microtask programming

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
31
0
1

Year Published

2017
2017
2021
2021

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 75 publications
(32 citation statements)
references
References 18 publications
0
31
0
1
Order By: Relevance
“…Some even enable collaborative, decentralized coordination instead of step-by-step instructions [46,86]. As the area advanced, it began to make progress in achieving significantly more complex and interdependent goals [43], such as knowledge aggregation [30], writing [43,61,78], ideation [84,85], clustering [12], and programming [11,50].…”
Section: Crowdsourcing Workflowsmentioning
confidence: 99%
See 1 more Smart Citation
“…Some even enable collaborative, decentralized coordination instead of step-by-step instructions [46,86]. As the area advanced, it began to make progress in achieving significantly more complex and interdependent goals [43], such as knowledge aggregation [30], writing [43,61,78], ideation [84,85], clustering [12], and programming [11,50].…”
Section: Crowdsourcing Workflowsmentioning
confidence: 99%
“…Recent work instead sought to achieve complex goals by moving from microtask workers to expert workers. Such systems now support user interface prototyping [70], questionanswering and debugging for software engineers [11,22,50], worker management [28,45], remote writing tasks [61], and skill training [77]. For example, flash teams demonstrated that expert workflows can achieve far more complex goals than can be accomplished using microtask workflows [70].…”
Section: Crowdsourcing Workflowsmentioning
confidence: 99%
“…The great innovation of the use of microtasks in software development resides in the atomization of the work in portions that employ the minimum of effort and time in its conclusion [8]. Microtasks can be represented by a similar concept of division of labor into small tasks Microtasks represent a promising area of research because of the gaps that are perceived in the literature, this is reflected by the absence of a taxonomy on the microtask (microtask, microtask, micro-task, etc.)…”
Section: A Microtasksmentioning
confidence: 99%
“…Microtasks are simple CS activities with a short duration time that can be paralleled [8]. Thus microtasks employ reduced time and effort, in addition to a relatively low development cost [9].…”
Section: Introductionmentioning
confidence: 99%
“…This decomposition is done to decrease complexity and the time required to solve the work given that several smaller tasks that can be tackled in parallel. Depending on the size of each task, they can be either a microtask [8], which refers to minute-length tasks with low cognitive effort, as discussed in [3,6] or a complex and time-consuming sub-problem, which remain simpler than the original project. Nevertheless, it is worth noticing that the benefit of presenting a software project as a collection of sub-tasks might be lost by the effort of putting back together the small pieces of code.…”
Section: Introductionmentioning
confidence: 99%