Studio
A small studio, working carefully, one project at a time.
CINDERBLOCK PRODUCTIONS LTD is an independent technology and digital production studio. The following pages describe how the studio is put together, what it believes about the work, and how it collaborates with the organisations that hire it.
§ 01
Overview
The studio was formed around a simple observation: organisations that treat software as a durable asset consistently outperform those that treat it as a disposable one. Everything about how we operate — team size, engagement length, tooling choices, the way we write things down — follows from that starting point.
We are a compact team of engineers, designers and producers who prefer to be responsible for entire pieces of work rather than fragments of them. We take on a small number of engagements each year so that each one receives the attention it needs.
§ 02
Mission
To help organisations build technology that they will still be glad to own five years from now.
A great deal of software is written quickly, works briefly and quietly becomes a burden. We exist to build the other kind — systems whose structure is legible, whose behaviour is understood, and whose maintenance is a routine activity rather than a periodic emergency.
In practice this means engaging early, writing carefully, and being willing to say when a piece of work should not be done, or should be done in a smaller form than originally proposed.
§ 03
Working principles.
A short list of the beliefs that govern how the studio operates day to day. They are not aspirational — they describe how the work actually gets done.
- 01
Small teams, complete responsibility
The engineer who writes the code owns its behaviour in production. There are no handovers to a separate maintenance team.
- 02
Written decisions
Every meaningful architectural decision is written down at the time it is made, in the repository, next to the code it affects.
- 03
Boring where it matters
We favour well-understood technology in the places most likely to fail. Novelty is reserved for domains where it earns its keep.
- 04
Slow is smooth, smooth is fast
Small, reviewable changes ship faster over any horizon longer than a week than large, ambitious ones do.
- 05
No premature abstractions
The right shape of a system is discovered, not designed. We defer generalisation until the pattern is proven.
- 06
Client on the inside
The client sees the same repository, tickets and environments the team does. There is no separate 'client view' of the work.
Plate — Structure over decoration
§ 04
Approach to digital production.
We approach production the same way a good publisher approaches an issue: structure first, then hierarchy, then texture. The scaffolding is invisible to the reader, but it is what makes everything else possible.
In practical terms this means treating design systems, editorial workflows, content models and delivery pipelines as first-class engineering work — not as configuration to be figured out at the end.
When the underlying production system is well-built, the surface work — the campaigns, the marketing sites, the product releases — becomes noticeably easier and more consistent over time.
§ 05
Collaboration.
We do not describe the studio as a vendor and we do not describe our clients as customers. Engagements work best when the studio's team and the client's team behave as a single working group with a shared repository, shared priorities and shared responsibility for the outcome.
In practice this means being present in the same planning conversations, using the same issue tracker, and being available for questions on the same timescale that an internal colleague would be.
It also means being direct. When we disagree with a proposed direction we say so, in writing, with our reasoning attached. Polite disagreement is a feature of a good engagement, not a failure of one.
§ 06
Quality standards.
A defined baseline that every piece of work leaves the studio meeting, regardless of size or timeline.
Version-controlled, from day one
Everything, including infrastructure definitions and documentation, lives in a reviewable repository.
Automated verification
Tests, type checks and linting run on every change; nothing merges without them.
Observable in production
Logs, metrics and traces are present before the system is called live, not added afterwards.
Documented for successors
Every project ends with a written handover that a new team can act on without further input.
Accessible by default
Interfaces meet accessibility guidelines as a delivery requirement, not an audit exercise.
Security-reviewed proportionately
Threat modelling and dependency review appropriate to the risk profile of the system.
§ 07 · Long view
A studio that gets better the longer it exists.
The studio is designed to compound. Each engagement adds to a shared body of methods, tools and internal documentation that makes the next one easier.
We are deliberately not trying to grow quickly. Adding people faster than we can integrate them is the most reliable way to make the work worse.
The long-term goal is a body of work that is recognisable in its craftsmanship regardless of which member of the studio produced it.
§ 08 · Reach us
Correspondence.
All initial correspondence is handled by email. A brief description of the project and its context is enough to begin.
- Studio
- CINDERBLOCK PRODUCTIONS LTD
- nicholascooper1957@gmail.com
- Domain
- cinderblockpictures.com
- Language
- English