MétaCan
Menu
Back to cohort
Record W2008189479 · doi:10.1109/vlhcc.2009.5295312

Attacking information overload in software development

2009· article· en· W2008189479 on OpenAlex
Gail C. Murphy

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldDecision Sciences
TopicPersonal Information Management and User Behavior
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsComputer scienceProgrammerInformation overloadTask (project management)RSSSoftware developmentSoftwareDomain (mathematical analysis)Field (mathematics)Software engineeringInterface (matter)TraverseWorld Wide WebProgramming languageOperating system

Abstract

fetched live from OpenAlex

The productivity of software developers is under constant attack due to a continual inundation of information: source code is easier and easier to traverse and to find, email inboxes are stuffed to capacity, RSS feeds and tweets provide a continual stream of technology updates, and so on. To enable software developers to work more effectively, tools are often introduced that provide even more information. The effect of more and more tools producing more and more information is placing developers into overload. To combat this overload, we have been building approaches rooted in structure and inspired by human memory models. As an example, the Mylyn project packages and makes available the structure that emerges from how a programmer works in an episodic-memory inspired interface. Programmers working with Mylyn see only the information they need for a task and can recall past task information with a simple click. We have shown in a field study that Mylyn makes programmers more productive; the half a million programmers now using Mylyn seem to agree. In this talk, I will describe the overload faced by programmers today and discuss several approaches we have developed to attack the problem, some of which may also pertain beyond the domain of software development.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.914
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.003
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.002

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.250
GPT teacher head0.437
Teacher spread0.187 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it