I build the systems businesses depend on.
Whether it's a national payment platform or the everyday tools a growing business runs on, I care about the same things: stability, accuracy, and code the next person can actually maintain.
These are platform-wide figures for systems I've contributed to. Full context on the Work page.
01 / Working software in production
You describe the problem and get back a system your business can run on, live and serving real users. Scoping and delivery stay joined up from the first requirement through launch, so what you asked for in week one is what actually ships.
02 / An architecture you can afford to keep
Most businesses do better with one well-organised codebase than a fleet of services. Built that way, your system costs less to host and is quicker to change when your plans shift. It also stays legible to any developer who picks it up after me.
03 / One steady point of contact
The person you scope the work with is the same one who sees it through, which keeps decisions from waiting on handoffs. Larger builds bring in extra hands when needed, and your contact doesn't change.
Plain English, always
When there's a trade-off (speed vs. cost, buy vs. build), I'll explain it in plain terms. You won't need a translator.
Boring technology, on purpose
Proven patterns over trending ones. Fewer moving parts means fewer 2am pages.
First we agree on what the actual problem is. Writing code before that just means rework later.
You'll get regular updates while I build, so you always know where things stand. And I stick to well-understood patterns that stay stable as the system grows.
The code and the data are yours, fully. Documentation comes with the handover.
dneey/laravel-cloudwatch
PackageAn AWS CloudWatch logging driver for Laravel. I wrote it because distributed apps on AWS were harder to debug than they needed to be.
Have a project in mind? Let's talk.
I take on a small number of projects at a time. Tell me what you're building, over email or a short call, and I'll get back to you within a day or two, even if the answer is "not yet."