About

Focused software, with the implementation made understandable.

I’m Shane Golding. I build tools, websites, Linux services, and browser experiments around specific problems and clear operating constraints.

From service operation to interface details

Systems that can be operated

The webcam streaming project includes health checks, startup recovery, and a rollback path alongside the core stream.

Automation with human checkpoints

The Discord bridge combines queued work and persistent threads with explicit human approvals and auditable activity.

Interactions that stay in context

Accessible Snake scopes game keys to its focused region, provides touch controls, and reports state changes as text.

A practical default for project decisions

  1. 01

    Start with the constraint

    Define the problem, runtime, inputs, and failure cases before adding surface area.

  2. 02

    Keep important state explicit

    Queues, approvals, game states, health checks, and recovery paths should be visible in the design.

  3. 03

    Prefer understandable parts

    Separate core logic from interface and platform concerns so each part can be inspected and tested.

  4. 04

    Design for more than one input

    Keyboard, touch, status text, and normal document navigation are part of the experience, not post-build extras.

A public example of the same approach

This website uses hand-written HTML, CSS, and JavaScript with no framework, build step, external font, analytics, or advertising tracker. Pages remain navigable without JavaScript. The Snake engine is separated from its Canvas UI and covered by Node tests.

  • Static GitHub Pages deployment
  • Semantic pages and visible focus states
  • Reduced-motion support
  • Deterministic game-engine tests

Have a focused problem to work through?

Email is the simplest way to start a conversation.

mail@shanegolding.net