How do we read algorithms? A case study
The DOI matches its Crossref record; 2 of the 2 references it cites were found in a registry or an index.
Abstract
The authors report on an experiment that explored the way subjects view an algorithm, written in Pascal, and the graphical representation of its behavior. They designed the experiment to examine the influence of programming experience on how subjects view a short but complex algorithm, and they analyzed the scan patterns of eye movement for subjects at two experience levels. They describe the experimental procedure in detail, and discuss the results. An important finding was that all subjects needed numerous fixations in most areas of the algorithm and spent more time viewing relevant slide areas than did subjects in studies using simple text. This supports the hypothesis that viewing strategies for algorithms differ from those for prose.>
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 theory of reading: From eye fixations to comprehension.
Just, M. A., & Carpenter, P. A. (1980) · Psychological Review · doi:10.1037/0033-295x.87.4.329 · Cited by 5,220
Chase, W. G., & Simon, H. A. (1973) · Cognitive Psychology · doi:10.1016/0010-0285(73)90004-2 · Cited by 4,479
Cited by
Using psycho-physiological measures to assess task difficulty in software development
Fritz, T., Begel, A., Müller, S. C., Yigit-Elliott, S., & Züger, M. (2014) · Proceedings of the 36th International Conference on Software Engineering · doi:10.1145/2568225.2568266 · Cited by 262
“In their study, they used eye fixation as a measure of attention, classified code into 5 categories from easy to hard and found that highexperienced developers use less time on comments and more time on complex statements than low experienced developers [16].”
MethodImproving automated source code summarization via an eye-tracking study of programmers
Rodeghero, P., McMillan, C., McBurney, P. W., Bosch, N., & D'Mello, S. (2014) · Proceedings of the 36th International Conference on Software Engineering · doi:10.1145/2568225.2568247 · Cited by 198
“For example, during maintenance tasks, some programmers follow a “systemic” strategy aimed at understanding how different parts of the code interact [30, 38].”
BackgroundMethodInfluentialEye Movements in Code Reading: Relaxing the Linear Order
Busjahn, T., Bednarik, R., Begel, A., Crosby, M., Paterson, J. H., Schulte, C., Sharif, B., & Tamm, S. (2015) · 2015 IEEE 23rd International Conference on Program Comprehension · doi:10.1109/icpc.2015.36 · Cited by 176
“One of the pioneering studies of the role of gaze in programming [9] suggests that viewing strategies when reading short, but complex algorithms differ from those of natural language.”
BackgroundSelf-citation(2015) · doi:10.5555/2818754.2818838 · Cited by 111
How Readable is Model-generated Code? Examining Readability and Visual Inspection of GitHub Copilot
Al Madi, N. (2022) · Proceedings of the 37th IEEE/ACM International Conference on Automated Software Engineering · doi:10.1145/3551349.3560438 · Cited by 50
“These metrics have been used extensively in psychology and software engineering research [20], with some of the earliest studies using fixation count and fixation duration to find the AOIs that attract more attention [8, 9, 23].”
Method
Metadata
- Authors
- Crosby, M. E., & Stelovsky, J.
- Venue
- Computer
- Published
- 1990-01
- Volume
- 23
- Issue
- 1
- Pages
- 25-35
- ISSN
- 0018-9162 (ISSN-L)
- OpenAlex
- W2142391150
- Cited by
- 174
- References
- 2
- FWCI
- 4.08
- Type
- journal article
- 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
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.