Deep intellisense: a tool for rehydrating evaporated information
The DOI matches its Crossref record; 5 of the 5 references it cites were found in a registry or an index.
Abstract
Software engineers working in large teams on large, long-lived code-bases have trouble understanding why the source code looks the way does. Often, they answer their questions by looking at past revisions of the source code, bug reports, code checkins, mailing list messages, and other documentation. This process of inquiry can be quite inefficient, especially when the answers they seek are located in isolated repositories accessed by multiple independent investigation tools. Prior mining approaches have focused on linking various data repositories together; in this paper we investigate techniques for displaying information extracted from the repositories in a way that helps developers to build a cohesive mental model of the rationale behind the code. After interviewing several developers and testers about how they investigate source code, we created a Visual Studio plugin called Deep Intellisense that summarizes and displays historical information about source code. We designed Deep Intellisense to address many of the hurdles engineers face with their current techniques, and help them spend less time gathering information and more time getting their work done.
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
A 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
Information Needs in Collocated Software Development Teams
Ko, A. J., DeLine, R., & Venolia, G. (2007) · 29th International Conference on Software Engineering (ICSE'07) · doi:10.1109/icse.2007.45 · Cited by 499 · cited 1×
“Studies of software developers’ information needs [3, 8] have shown that their most common question is “why?” Why is this”
BackgroundSplitting the organization and integrating the code: Conway's law revisited
Herbsleb, J. D., & Grinter, R. E. (1999) · Proceedings of the 21st international conference on Software engineering · doi:10.1145/302405.302455 · Cited by 425
People, organizations, and process improvement
Perry, D. E., Staudenmayer, N. A., & Votta, L. G. (1994) · IEEE Software · doi:10.1109/52.300082 · Cited by 401
Questions programmers ask during software evolution tasks
Sillito, J., Murphy, G. C., & De Volder, K. (2006) · Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering · doi:10.1145/1181775.1181779 · Cited by 270 · cited 1×
“Studies of software developers’ information needs [3, 8] have shown that their most common question is “why?” Why is this”
Background
Cited by
Mining StackOverflow to turn the IDE into a self-confident programming prompter
Ponzanelli, L., Bavota, G., Di Penta, M., Oliveto, R., & Lanza, M. (2014) · Proceedings of the 11th Working Conference on Mining Software Repositories · doi:10.1145/2597073.2597077 · Cited by 240
“Seminal tools, such as eRose [43], Hipikat [9] and DeepIntellisense [14], suggest project artifacts in the IDE aiming at providing developers with additional information on specific parts of the system.”
Using information fragments to answer the questions developers ask
Fritz, T., & Murphy, G. C. (2010) · Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1 · doi:10.1145/1806799.1806828 · Cited by 163
Hard-to-answer questions about code
LaToza, T. D., & Myers, B. A. (2010) · Evaluation and Usability of Programming Languages and Tools · doi:10.1145/1937117.1937125 · Cited by 141
(2012) · doi:10.5555/2666719.2666725 · Cited by 74
Harnessing Stack Overflow for the IDE
Bacchelli, A., Ponzanelli, L., & Lanza, M. (2012) · 2012 Third International Workshop on Recommendation Systems for Software Engineering (RSSE) · doi:10.1109/rsse.2012.6233404 · Cited by 60
Metadata
- Authors
- Holmes, R., & Begel, A.
- Venue
- Proceedings of the 2008 international working conference on Mining software repositories
- Publisher
- ACM
- Published
- 2008-05-10
- Pages
- 23-26
- OpenAlex
- W2032514319
- Cited by
- 54
- References
- 5
- FWCI
- 2.89
- 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: Deep intellisense: a tool for rehydrating evaporated information. https://app.cochat.ai/papers/10.1145/1370750.1370755
- The paper
- Holmes, R., & Begel, A. (2008). Deep intellisense: a tool for rehydrating evaporated information. Proceedings of the 2008 international working conference on Mining software repositories. https://doi.org/10.1145/1370750.1370755
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.