Skip to content
Plate Circle

About · Chapter I

A studio that believes software is a craft, and behaves accordingly.

§ Introduction

Who we are.

Plate Circle Ltd is an independent software engineering practice. We work with a small number of clients at a time, taking each project from an initial description of the problem through design, implementation, and the long tail of ownership that comes after launch.

We are not a body-shop, not a template studio, and not a marketing agency. Everything we produce is written for the specific situation of the client in front of us.

An empty modern meeting room lit by warm morning light through tall windows

§ Purpose

Why the studio exists.

A great deal of the software people use every day is quietly disappointing. It works, but only just. It grows without design. It becomes brittle before it becomes valuable.

We started Plate Circle to run a practice that resists that path — to build software that the people using it are not sorry to depend on, and that the people maintaining it are not embarrassed to inherit.

§ Philosophy

Every choice — a dependency, a boundary, an abstraction — is a small promise to the people who will keep the system alive when we are no longer in the room. We try to make promises we would want to inherit.
Close-up of source code on a dark monitor with warm side light

§ Approach

How we approach technology projects.

We favour short cycles, honest scoping, and steady delivery of small, working pieces. Where possible we prefer the well-established option over the fashionable one, and we treat any decision that will be expensive to reverse as a decision that deserves extra thought before it is made.

§ Collaboration

Principles of working together.

Software work happens between people first and between systems second. These are the habits that make the collaboration honest and productive on both sides.

  1. 01

    Small commitments

    We prefer clear, small commitments over vague, large ones — and we keep them.

  2. 02

    Written thinking

    Important decisions are written down, so both sides can look at the same thing.

  3. 03

    Honest scope

    We say when a request is outside scope, and we say why, before it becomes a surprise.

  4. 04

    Direct access

    You speak to the people doing the work, not to a layer of managers.

  5. 05

    Steady cadence

    Progress is visible on a rhythm both sides can plan around.

  6. 06

    Clean handovers

    Documentation and access are treated as part of the deliverable, not an afterthought.

§ Quality

Software quality standards.

Quality, for us, is not a property added at the end. It is the accumulation of many small decisions taken well throughout the life of the project: how modules are shaped, how data flows are named, how errors are handled, how tests are written before behaviour is committed to.

  • Typed contracts between components, checked in the build
  • Automated tests as the specification, not a formality
  • Continuous integration on every change, not on release
  • Clear separation between application code and its infrastructure
  • Readable code, because most of a program's life is being read

§ Security

Security and reliability mindset.

Security is treated as a design property that has to be present from the first commit. We assume that mistakes will happen, that dependencies will drift, and that credentials will need to be rotated — and we design so that each of those things has an obvious place to happen safely.

Reliability is the same discipline seen from another angle. Systems that fail in predictable ways are far easier to keep running than systems that fail in creative ones.

§ Communication

How we communicate on a project.

Written correspondence is the backbone of every engagement. Email is our primary channel; short calls exist to unblock decisions, and their outcomes are always recorded afterwards.

We produce brief weekly notes that describe what changed, what is next, and what is blocked. When a change of direction is needed, it is discussed openly and documented before any code is touched.

A brushed metal plate with concentric rings, an abstract mark of continuity

§ Vision

A long-term view of a small practice.

We are content to remain small. That is not a limitation — it is the shape that lets us take the work seriously. Our long-term view is to keep building software that behaves well for a long time, alongside clients whose problems reward close attention.

§ Reach us

Written enquiries are welcome and answered promptly.

Email
kathleensa58@gmail.com
Web
platedining.com
Entity
PLATE CIRCLE LTD