CoChat

TODO or to bug: exploring how task annotations play a role in the work practices of software developers

Storey, Margaret-Anne, Ryall, Jody, Bull, R. Ian, Myers, Del, Singer, Janice · 2008 · Proceedings of the 13th international conference on Software engineering - ICSE '08
Cited by 120

The DOI matches its Crossref record; 2 of the 2 references it cites were found in a registry or an index.

Abstract

Software development is a highly collaborative activity that requires teams of developers to continually manage and coordinate their programming tasks. In this paper, we describe an empirical study that explored how task annotations embedded within the source code play a role in how software developers manage personal and team tasks. We present findings gathered by combining results from a survey of professional software developers, an analysis of code from open source projects, and interviews with software developers. Our findings help us describe how task annotations can be used to support a variety of activities fundamental to articulation work within software development. We describe how task management is negotiated between the more formal issue tracking systems and the informal annotations that programmers write within their source code. We report that annotations have different meanings and are dependent on individual, team and community use. We also present a number of issues related to managing annotations, which may have negative implications for maintenance. We conclude with insights into how these findings could be used to improve tool support and software process.

Overview

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1145/1368088.1368123

Cites

2 of 2 references verified0 citation errors · 0 not checkable

Statistics

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

A few free checks a day · papers already verified open instantly · results are public

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Citations

Cites

  • How are Java software developers using the Eclipse IDE?

    Murphy, G. C., Kersten, M., & Findlater, L. (2006) · IEEE Software · doi:10.1109/ms.2006.105 · Cited by 413 · cited 2×

    “More effective methods would involve directly observing the programmers or indirectly observing their actions through instrumentation of their IDEs as Murphy did in [ 13 ].”
    BackgroundMethod
  • Double-level languages and co-operative working

    Robinson, M. (1991) · AI & Society · doi:10.1007/bf01891356 · Cited by 132 · cited 1×

    “In particular we saw evidence of a gap between what Robinson calls the “formal level of language” [17] supported by a bug or issue tracking system and the “cultural level”, supported by task annotations.”
    Background

Show all 2 references

Cited by

See all 120

Metadata

Authors
Storey, M.-A., Ryall, J., Bull, R. I., Myers, D., & Singer, J.
Venue
Proceedings of the 13th international conference on Software engineering - ICSE '08
Publisher
ACM Press
Published
2008
Pages
251
ISSN
0270-5257 (ISSN-L)
OpenAlex
W1500946169
Cited by
120
References
2
FWCI
6.56
Type
conference paper
Language
en
Open access
closed

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: TODO or to bug: exploring how task annotations play a role in the work practices of software developers. https://app.cochat.ai/papers/10.1145/1368088.1368123
The paper
Storey, M.-A., Ryall, J., Bull, R. I., Myers, D., & Singer, J. (2008). TODO or to bug: exploring how task annotations play a role in the work practices of software developers. Proceedings of the 13th international conference on Software engineering - ICSE '08. https://doi.org/10.1145/1368088.1368123

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.