CACrown ArchivesThe cinema collection
Menu
Research dossier · Science & Nature

Hackathon

event in which groups of software developers work at an accelerated pace

Specimen drawers, botanical folios and brass scientific instruments under study light
Science and natureInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionAug 25, 2026
Entity authorityQ46855
Source-derived summary

A hackathon (also known as a hack day, hackfest, datathon or codefest; a portmanteau of hacking and marathon) is an event where people engage in rapid and collaborative engineering over a relatively short period of time, such as 24 or 48 hours in person or several days online. They are often run using agile software development practices, such as sprint-like design wherein computer programmers and others involved in software development, including graphic designers, interface designers, product managers, domain experts, and others collaborate intensively on engineering projects, such as software engineering.

The goal of a hackathon is to create functioning software or hardware by the end of the event. Hackathons tend to have a specific focus, which can include the programming language used, the operating system, an application, an API, or the subject and the demographic group of the programmers. In other cases, there is no restriction on the type of software being created or the design of the new system.

In addition to creating functional software or hardware, hackathons can help participants develop skills like problem solving, critical thinking, creativity, team work, communication and time management. Hackathons can also lead to formation of new companies, finding innovative solutions to real-world problems, or building a community around a particular technology or cause.

Etymology

The word "hackathon" is a portmanteau of the words "hack" and "marathon", where "hack" is used in the sense of exploratory programming, not its alternate meaning as a reference to breaching computer security.

OpenBSD's apparent first use of the term referred to a cryptographic development event held in Calgary on June 4, 1999, where ten developers came together to avoid legal problems caused due to export regulations of cryptographic software from the United States. Since then, a further three to six events per year have occurred around the world to advance development, generally on university campuses.

Editorial summary

Begin with the source’s own compact description: “Hackathon” is event in which groups of software developers work at an accelerated pace. The dossier treats that line as a proposition to test through Hackathon, event and groups, not as a finished interpretation.

Editorial reviewUseful for establishing the present vocabulary of the subject while preserving a route back to the evidence on which that vocabulary rests. The current lead gives the account dated anchors—1999—that can be checked directly. The selected authority fields contribute no independent date. For this dossier, Hackathon, event and groups is the immediate research focus.
Editorial analysis

Why this record matters

The phrase “event in which groups of software developers work at an accelerated pace” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.

Evidence profile

The date and method of observation matter as much as the stated conclusion, especially where classification or consensus has changed. The source revision retrieved here is dated Aug 25, 2026. The linked authority identifier is Q46855. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1999.

Critical limits

A general summary may omit uncertainty, sample limits or methodological disagreement that is explicit in the technical record. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.

Best used for
  • Current terminology
  • Classification context
  • Finding cited technical literature
Verify next

Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.

Three-step research path

  1. Establish the record: confirm the title “Hackathon”, its source revision and the description used here.
  2. Expand the search: follow Hackathon primary sources, Hackathon archive and Hackathon research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “Hackathon”?
  2. Is the terminology current, historical or disputed?
  3. Which observation, specimen, dataset or publication supports the account?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from Hackathon” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.