I build web applications end to end
Full-stack development. I take a project from an empty repository to something running in production — database, API, interface, and the deployment that carries it.
What I do
Three ways I usually get brought in. Most projects turn out to be some combination of them.
New builds
You have a product to build and no codebase yet. I handle the architecture, database, API, interface and deployment, and hand over something you or your team can actually maintain afterwards.
Existing systems
Inherited code, pages that have got slow, a feature that keeps breaking. I work out what is actually wrong before changing anything — which is usually cheaper than the rewrite it looked like it needed.
Getting to production
Building it is half the job. I set up the deployment, monitoring and backups so that shipping is routine rather than an event, and so you find out when something breaks before your users tell you.
About
I'm a full-stack developer working with clients wherever they happen to be. My background is backend — Java and Spring on AWS — and I've moved toward owning the whole slice, interface included. On a small team that means fewer handoffs, and someone who can follow a problem from the browser down to the database without passing it along.
I like the parts of the job most people would rather skip: reading unfamiliar code, tracking down the bug that only shows up in production, making a deployment boring and repeatable. If you want someone who will tell you when the simpler option is the better one, that's the job I prefer doing.
Get in touch
Tell me roughly what you're building and what your timeline looks like, and I'll tell you honestly whether I'm the right fit.
Prefer email? hello@iamlukia.com