MétaCan
Menu
Back to cohort
Record W1585844169 · doi:10.1109/fie.1998.736882

Teaching history in computing

2002· article· en· W1585844169 on OpenAlexaff
John Impagliazzo, G. Davies, J.A.N. Lee, Mary Williams

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicHistory of Computing Technologies
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsHistory of computingTask (project management)Computer scienceCurriculumPerspective (graphical)Joint (building)Field (mathematics)Engineering ethicsMathematics educationData scienceArtificial intelligenceSociologyPedagogyPsychologyEngineering

Abstract

fetched live from OpenAlex

Summary form only given. For the computing discipline, history seldom receives status. From a cultural standpoint history broadens one's perspective on the field and lets students and scholars explore the inner thinking of people and the events they produced. From a practical standpoint, history enables individuals and enterprises to learn from the events of the past and to improve on experiences. Both views are necessary to create an informed computing professional. Teachers often ignore history of computing when teaching their computing courses. The typical case is that educators mention some facts or important milestones usually related to hardware and the people responsible for these. The discussion then moves quickly to other topics. This is unfortunate, because we can learn much from history. History is the best teacher to assess the meaningful evolution of the computing profession. The IFIP Joint (TC3-TC9) Task Group has examined this concern and is producing a report entitled: History in the Computing Curriculum. The report addresses the need to include history in the curriculum and serves as a basis for this proposal. It also provides educators, whose formal study of computing history is minimal or nonexistent, ways in which to teach computing history in an educational environment. This paper presents the work of the IFIP Joint Task Group to a computing and engineering audience.

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.

How this classification was reachedexpand

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.000
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: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.736
Threshold uncertainty score0.381

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.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.0010.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.036
GPT teacher head0.222
Teacher spread0.186 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designSimulation or modeling
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations0
Published2002
Admission routes1
Has abstractyes

Explore more

Same topicHistory of Computing TechnologiesFrench-language works237,207