Skip to content

Press and enquiries

Understand the machine.
Make something with it.

Code198x is developing a games development and programming curriculum that uses vintage computers to make the workings of software understandable.

A short description

Code Like It’s 198x teaches programming and game development through vintage computers. Readers build games, investigate how the machine works and connect that understanding to the choices they make with modern tools. The lessons are free to read, with an accompanying encyclopaedia, reusable programming patterns and open-source development tools.

You are welcome to use this description when introducing the project. About Code198x explains the purpose in more depth.

Why vintage machines?

Small programs and visible constraints make it possible to connect a game’s rules, graphics and sound to its data and execution. Readers can ask what a variable represents, why an animation stutters or how a program talks to a device, then investigate a concrete example.

The purpose is to understand and create. Historical sources help explain the choices people made, while comparisons between systems show what transfers and what changes. Modern relevance comes through specific questions about responsiveness, representation, algorithms and limited resources.

What readers can explore

Programming and games

Foundations uses language-neutral pseudocode. The initial system focus is the ZX Spectrum, Commodore 64, Commodore Amiga and NES. Their system pages lead to the available tracks and lessons.

Context and techniques

The Vault connects machines, games, people and computing history. The Pattern Library offers concrete techniques to adapt, with their machine requirements and trade-offs.

The curriculum is in development. A listed machine is not a completed course. The Craft’s current Maths for Games and Game Feel pages are outlines for further teaching material. Wider system coverage and projects using expansions are part of the intended direction, not claims that those lessons already exist.

The curriculum map explains the organisation. What’s New records published additions; dates and claims in coverage should refer to the material available at the time.

People and tools

Code198x was started by Steve Hill, a software engineer. Contributors can help with teaching, code, research, illustration and testing. The contribution page points to scoped work, including tasks that welcome review reports without requiring code changes.

The wider 198x family develops tools for assembly, builds, emulation and working with vintage media. These projects have distinct scopes; tool support for a machine does not establish curriculum coverage.

AI assists development and drafting. Claims still need appropriate sources and code needs appropriate checks. Sources & Standards distinguishes proposals, source checks, builds and observed execution. It does not claim that every page or program has been verified on original hardware.

Access and reuse

The lessons are free to read. Original prose is available underCC BY 4.0, with attribution and the required notices. The maintained code samples are published under the MIT licence. Check the licence and attribution attached to material you wish to reuse; third-party images and software have their own terms.

Some activities require tools or system ROMs. Requirements depend on the chosen language and machine; see setup guidance. Free access to the curriculum does not mean every target’s software or hardware is supplied.

Using our name and logo

Use Code198x or Code Like It’s 198x when referring to the project. You do not need to ask permission to refer to us in an article, talk, video, reading list or account of something you built or taught.

You may reproduce the logo unaltered to identify the project. Do not recolour, restyle or crop it, use it as your own branding, or imply endorsement, partnership or approval. For other uses, contact us.

Contact and further information

For interviews, questions or image requests, contact Steve through the Code198x Discord. Include the publication or event, subject and deadline. Please do not post confidential information in a public channel.

Find the repositories on GitHub, follow project updates, or read development stories. Technical and historical corrections are welcome through the correction routes.