MétaCan
Menu
Back to cohort
Record W3152220058 · doi:10.1115/1.4050734

Are Two Heads Better Than One for Computer-Aided Design?

2021· article· en· W3152220058 on OpenAlex

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

VenueJournal of Mechanical Design · 2021
Typearticle
Languageen
FieldEngineering
TopicDesign Education and Practice
Canadian institutionsUniversity of TorontoUniversity of New Brunswick
Fundersnot available
KeywordsComputer sciencePair programmingSoftwareEngineering design processQuality (philosophy)Software designHuman–computer interactionSoftware engineeringSoftware developmentEngineeringProgramming language

Abstract

fetched live from OpenAlex

Abstract With the availability of cloud-based software, ubiquitous internet, and advanced digital modeling capabilities, a new potential has emerged to design physical products with methods previously embraced by the software engineering community. One such example is pair programming, where two coders work together synchronously to develop one piece of code. Pair programming has been shown to lead to higher-quality code and user satisfaction. Cutting-edge collaborative computer-aided design (CAD) technology affords the possibility to apply synchronous collaborative access in mechanical design. We test the generalizability of findings from the pair programming literature to the same dyadic configuration of work in CAD, which we call pair CAD. We performed human subject experiments with 60 participants to test three working styles: individuals working by themselves, pairs sharing control of one model instance and input, and pairs able to edit the same model simultaneously from two inputs. We compare the working styles on speed and quality and propose mechanisms for our observations via interpretation of patterns of communication, satisfaction, and user cursor activity. We find that on a per-person basis, individuals were faster than pairs due to coordination and overhead inefficiencies. We find that pair work, when done with a single shared input, but not in a parallel mode, leads to higher-quality models. We conclude that it is not software capabilities alone that influence designer output; choices regarding work process have a major effect on design outcomes, and we can tailor our process to suit project requirements.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.254
Threshold uncertainty score0.613

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.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

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.103
GPT teacher head0.309
Teacher spread0.206 · 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