Oneiros

Notes

Occasional notes on how we think about the work.

Software that outlives its authors

Most software is written as though the people who wrote it will always be there to explain it. They will not. The measure we hold ourselves to is whether a capable stranger, years from now, could open the work and understand why each piece is there.

That standard changes daily decisions. It argues for fewer dependencies, for names that say what a thing is, and for documents written while the reasoning is still fresh. None of it is glamorous. All of it is what makes software an asset and not a liability.

Why we stay small

Growth is the default ambition of a services firm, and we have declined it for thirty years. A larger firm must keep its people busy, and that need quietly shapes the advice it gives.

Staying small lets us say no. It lets the people who design a system be the people who build it. And it means a client always knows exactly who is doing the work.

On discretion

We are sometimes asked why there are no client names here. The answer is simple. The work belongs to the people who commissioned it, and so does the decision to speak about it.

Discretion is also practical. Clients tell us more, earlier, when they know it will go no further. Better information makes better software.