"Breaking the code", moving between private and public work in collaborative software development
The DOI matches its Crossref record; 9 of the 9 references it cites were found in a registry or an index.
Abstract
Software development is typically cooperative endeavor where a group of engineers need to work together to achieve a common, coordinated result. As a cooperative effort, it is especially difficult because of the many interdependencies amongst the artifacts created during the process. This has lead software engineers to create tools, such as configuration management tools, that isolate developers from the effects of each other's work. In so doing, these tools create a distinction between private and public aspects of work of the developer. Technical support is provided to these aspects as well as for transitions between them. However, we present empirical material collected from a software development team that suggests that the transition from private to public work needs to be more carefully handled. Indeed, the analysis of our material suggests that different formal and informal work practices are adopted by the developers to allow a delicate transition, where software developers are not largely affected by the emergent public work. Finally, we discuss how groupware tools might support this transition.
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.
Integrity signals
Registry
Cites
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.
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
Star, S. L., & Griesemer, J. R. (1989) · Social Studies of Science · doi:10.1177/030631289019003001 · Cited by 10,847
Hutchins, E. (1995) · doi:10.7551/mitpress/1881.001.0001 · Cited by 10,801
Awareness and coordination in shared workspaces
Dourish, P., & Bellotti, V. (1992) · Proceedings of the 1992 ACM conference on Computer-supported cooperative work - CSCW '92 · doi:10.1145/143457.143468 · Cited by 2,550 · cited 3×
“parallel and contain information that only one user can see and edit, allowing him to create drafts that later will be shared with the other co-workers [7].”
BackgroundInfluentialSelf-citationA field study of the software design process for large systems
Curtis, B., Krasner, H., & Iscoe, N. (1988) · Communications of the ACM · doi:10.1145/50087.50089 · Cited by 2,076
How a Cockpit Remembers Its Speeds
Hutchins, E. (1995) · Cognitive Science · doi:10.1207/s15516709cog1903_1 · Cited by 1,880 · cited 3×
“Furthermore, it is also well-known that, in some settings, making others’ work public facilitates the coordination of the activities [16] [17] and enables learning and greater efficiencies [20].”
BackgroundTaking CSCW seriously: Supporting articulation work
Schmidt, K., & Bannon, L. (1992) · Computer Supported Cooperative Work (CSCW) · doi:10.1007/bf00752449 · Cited by 1,043 · cited 1×
“All this extra-work performed by the different members of the MVP team is another form of articulation work [27] that occurs in cooperative software development.”
BackgroundThe Myth of the Paperless Office
Sellen, A. J., & Harper, R. H. R. (2001) · doi:10.7551/mitpress/4833.001.0001 · Cited by 902
The Intellectual Challenge of CSCW: The Gap Between Social Requirements and Technical Feasibility
Ackerman, M. S. (2000) · Human–Computer Interaction · doi:10.1207/s15327051hci1523_5 · Cited by 892
How does radical collocation help a team succeed?
Teasley, S., Covi, L., Krishnan, M. S., & Olson, J. S. (2000) · Proceedings of the 2000 ACM conference on Computer supported cooperative work · doi:10.1145/358916.359005 · Cited by 224
Cited by
Software Engineering for Machine Learning: A Case Study
Amershi, S., Begel, A., Bird, C., DeLine, R., Gall, H., Kamar, E., Nagappan, N., Nushi, B., & Zimmermann, T. (2019) · 2019 IEEE/ACM 41st International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP) · doi:10.1109/icse-seip.2019.00042 · Cited by 1,135
Social transparency in networked information exchange: a theoretical framework
Stuart, H. C., Dabbish, L., Kiesler, S., Kinnaird, P., & Kang, R. (2012) · Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work · doi:10.1145/2145204.2145275 · Cited by 100
“For example, a study of awareness in software development suggested that engineers found the email messages generated to notify them of individual changes to code disruptive, and struggled to keep up with the information contained within often keeping changes private to avoid disturbing others [71].”
BackgroundEarly Detection of Collaboration Conflicts and Risks
Brun, Y., Holmes, R., Ernst, M. D., & Notkin, D. (2013) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2013.28 · Cited by 82
“Developers eschew parallel work to avoid having to resolve conflicts when committing changes [19], or rush their work into the trunk to avoid being the developer who would have to resolve conflicts [13].”
BackgroundTerritorial Functioning in Collaborative Writing: Fragmented Exchanges and Common Outcomes
Larsen-Ledet, I., & Korsgaard, H. (2019) · Computer Supported Cooperative Work (CSCW) · doi:10.1007/s10606-019-09359-8 · Cited by 43
Metadata
- Authors
- de Souza, C. R. B., Redmiles, D., & Dourish, P.
- Venue
- Proceedings of the 2003 international ACM SIGGROUP conference on Supporting group work
- Publisher
- ACM
- Published
- 2003-11-09
- Pages
- 105-114
- OpenAlex
- W2116821290
- Cited by
- 113
- References
- 9
- FWCI
- 5.73
- 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: "Breaking the code", moving between private and public work in collaborative software development. https://app.cochat.ai/papers/10.1145/958160.958177
- The paper
- de Souza, C. R. B., Redmiles, D., & Dourish, P. (2003). "Breaking the code", moving between private and public work in collaborative software development. Proceedings of the 2003 international ACM SIGGROUP conference on Supporting group work. https://doi.org/10.1145/958160.958177
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.