Paddy Systems is not a consultancy. I build and maintain my own products, in public, around problems I understand well enough to keep small.
- Paddy Systems Ltd
- Relay / Mirror
- Building in public
How I choose what to build
I start with friction worth removing, then try very hard not to turn the answer into a product that does everything.
Working principles
- 01
Build the smallest useful thing
Ship the version that solves the problem, not the version that anticipates every adjacent problem.
- 02
Keep local workflows genuinely local
If a tool works on your machine, it should not need to send your work elsewhere to do so.
- 03
Prefer open, interoperable systems
Work with the stack already in place rather than asking for a stack to be rebuilt around me.
- 04
Be explicit about product boundaries
Say what a product does, what it does not do, and what has not shipped yet.
- 05
Earn complexity rather than assuming it
Every additional concept has to justify itself against the cost of learning it.
A more open web for more builders.
Good tools should remove friction without demanding that developers reshape their entire workflow around the tool.