Method

Writing code stopped being the expensive part of this work. What is left is choosing which tools to build on, and proving the result does what was asked.

Choosing the tools

It has to do the job today.

Roadmaps are marketing. If a tool is missing the one thing your process depends on and support says it is coming next quarter, the tool is missing it. I have replaced a popular scheduling application that kept changing direction with a smaller one that did the whole work on day one and had not changed its data format in years. The smaller one is still running.

Robust, maintained, and used by people other than me.

Before a tool goes into a client's business it has usually been running in mine. Chocolat Infini's orders, inventory and accounting have run on the same system since 2024. I look at how often it breaks, who fixes it, how fast, and what happens to your data if that stops.

The simplest thing that does the job.

The standard way to run many applications on one server is built for companies running thousands of them. For a business running fifteen, it adds a full-time job nobody has. There are simpler tools that do the same thing at your scale, and that are easy to understand and maintain for a simgle person.

Nothing that locks you in.

Your data has to come out in a format something else can read, and every tool has to be replaceable without rebuilding the rest. That rule costs a little flexibility up front, and it is the reason none of this becomes someone else's leverage over you later.

Proving it works

Requirements are written in plain language, tied to the business reason that justifies them. Every requirement has its test. The build runs in iterations against those tests, with something working at each checkpoint instead of one big delivery at the end.

Backups are restored on a schedule, because a backup nobody has ever restored is not a backup.

Where AI fits

I use AI tools every day and they make the build cheaper for you. They do not decide anything. A system that was six months of work in 2022 is six weeks now. The ways it can break did not shrink with it. That is why the test plan gets written before the first line of code.

Want to talk it through? Book a 30-minute call.