Prefer primary evidence.
Use original papers, manuals, code, interviews, archives and contemporaneous records whenever they exist. Institutional secondary sources remain valuable and are labeled honestly.
CodeHistory documents programming as a living human practice. Sources, revisions, contested claims and corrections are part of the product—not footnotes to it.
Use original papers, manuals, code, interviews, archives and contemporaneous records whenever they exist. Institutional secondary sources remain valuable and are labeled honestly.
“First,” “invented,” and “pioneer” are often more complex than a plaque suggests. Priority claims should state scope, evidence type and uncertainty.
People, organizations, methods, milestones and publications receive distinct records so relationships can be represented without collapsing identities.
The closer we are to an event, the less historical distance we have. Contemporary entries show their evidence and remain open to revision.
CodeHistory distinguishes contemporaneous primary records, later first-person recollections, institutional histories, independent retrospective reporting and editorial interpretation. A strong source is not automatically a primary source.
Named authors write under the CodeHistory editorial system, while the CodeHistory Research Desk is responsible for research standards, source discipline, review, revision notes and corrections. Articles expose publication date, research review, sources and revision history, and the archive invites stronger evidence when it appears.