Software should take work away, not add it.
If a system means somebody now keeps a spreadsheet alongside it, we built the wrong thing. That is the first test we apply, before any of the others.
Five things we hold to. They are written here so a client can hold us to them, which is the only reason to write anything like this down.
01/05
If a system means somebody now keeps a spreadsheet alongside it, we built the wrong thing. That is the first test we apply, before any of the others.
The shape of a system is chosen before there is any pressure to ship. After that, nobody has the time left to choose it.
Anyone can show you the path where every service is up and every form is filled in correctly. The other paths are the work.
If a piece of work is not worth doing, or something simpler would do the job, that is what we will tell you. It costs us a project and saves you one.
Handing over a repository is not delivery. Running the thing, and being reachable when it matters, is the part that decides whether the rest was worth doing.
What we are after says itself in one line: build software people are glad to use, and stay with it. Everything above is a way of getting there — something that takes work away rather than adding it, that holds up when a part of it breaks, and that somebody is still looking after long after the day it went live.
Contact
A website, an app, an online shop, an internal system, or a change to something you already have. Write to us and a person answers.
hello@rysellc.comBook a call