OPERATOR RECORD // PERSON BEHIND THE TERMINAL

PETERJONES

I’m a systems architect, programmer and writer in South West England. By day I design large technical systems. After hours I make small, strange ones for the browser.

▸ THREE WORKING MODES

WHAT I ACTUALLY DO

The same habits recur at different scales: understand the system, expose its seams, make the complicated thing legible.

MODE 01 // SYSTEMS

ARCHITECT

I design and explain enterprise technology: infrastructure, security, applications, integration and the operating models that keep them useful.

The work is part engineering, part translation. A sound architecture should survive both a design review and contact with the people who must run it.

▸ OUTPUT CHANNELS

THINGS I MAKE

A deliberately mixed cabinet. Serious tools and ridiculous experiments are allowed to share a shelf.

01 // SYSTEMS

ARCHITECTURES & MODELS

Reference architectures, security patterns, service models, decision records and diagrams intended to make complex estates governable.

02 // SOFTWARE

TOOLS & UTILITIES

Mostly Python, JavaScript and the browser: generators, image workflows, calculators, simulations and utilities built because a specific problem was annoying.

03 // INTERFACES

RETRO MACHINES

False desktops, obsolete metaphors, tiny games and interactive fragments that treat interface history as a material rather than a costume.

04 // FICTION

STRANGE STORIES

Occult systems, speculative machinery, cosmic horror, invented archives and worlds where the technical explanation usually makes things worse.

▸ CURRENT WORKBENCH

MATERIALS & MACHINES

Not a keyword cloud; just the things most likely to be open on the desk.

ACTIVE TOOLCHAIN

Windows and Linux systems, small computers, plain files and tools whose workings can still be inspected.

PYTHONHTML / CSS / JSRASPBERRY PIWINDOWSLINUXNETWORKSSECURITYSYSTEMS MODELLINGRETRO COMPUTINGIMAGE WORKFLOWSPHOTOGRAPHYSPECULATIVE FICTIONTWO DACHSHUNDS

▸ SITE RATIONALE

WHY 334DIGITAL EXISTS

This site is a place to put work that does not need to become a product, a post format or a personal brand. It can be useful, odd, unfinished, over-engineered or all four.

I like the web best when it behaves like a collection of places rather than a single endless feed. 334Digital is my contribution to that geography: hand-coded, static-first, source-readable and permanently under construction.

The name is a label, not a company. The cabinet is the point.

  1. Own the file, not merely the account.
  2. Make the complicated thing legible.
  3. Leave enough seams visible to learn from.
  4. Publish the interesting object before polishing away its character.