Fifteen years of shipping.

I have been building and automating software since 2011. I started with Python — writing automation and scripting that did the unglamorous work reliably: moving and cleaning data, driving APIs, and turning slow, repetitive manual tasks into scripts that simply ran on their own. That habit of automating the breakable, boring parts still shapes everything I build today.

From there I grew into full web development, taking projects end to end — architecture, backend, front end and deployment — usually as the only engineer on the project. Over the years that has spanned real-time data platforms, B2B portals, aggregation engines and payment integrations.

In 2019 I built and ran a UK hosting company. That meant specifying physical hardware, colocating it at Volta Data Centres in London, arranging network transit and peering with Cogent, and writing the automation that provisioned and billed customers. I was responsible for the machines, not just the code on them.

One of my earlier commercial products, back in 2015, was an international mobile airtime top-up service. It happened to accept Bitcoin as one payment option at a time when no processor offered that off the shelf, so I wrote the confirmation and reconciliation logic myself — but the product was reliable airtime delivery, not crypto.

How that shapes the work

Having been on call for infrastructure changes how you write software. I assume the network will fail, upstream APIs will return nonsense, and something will break at an inconvenient hour. So I build for it: retries with sensible backoff, idempotent operations, logging that actually helps at 3am, and failure modes that are visible rather than silent.

It also makes me sceptical of complexity that has not earned its place. If a flat file is faster and simpler than a database for a given job, I will use a flat file and tell you why.

How I work with clients

I work solo and take on a small number of projects at a time. You deal directly with the person writing the code — there is no account manager in between, and no handoff to a junior team once the work is won.

I work independently under the Jeemmo name — you deal directly with me, the person writing the code. I have been building for the web since 2011, and work day to day from Istanbul on UTC+3 — two hours ahead of London and one ahead of most of Europe. In practice that is a shared working day with UK and European clients: questions get answered the same day, and calls happen at reasonable hours for both of us. I work in English throughout.

Every project starts with a written scope and a fixed price. Work lands on a staging environment you can use throughout, payments are tied to milestones, and at handover you get the full source and infrastructure access. No lock-in.

How payment works

Every project runs on a written scope with a fixed price, split into milestones. You pay a deposit to start, then each milestone is invoiced as it is delivered — so you are never paying ahead of something you can already see working on a staging environment.

Ways to pay

Every payment comes with an itemised invoice. If your finance team needs a purchase order reference, particular invoice wording, or a supplier onboarding form completed, that is all fine — tell me at the start and I will work to your process.

Technical background

Backend

PHP, Node.js, Python, MySQL, SQLite, REST and WebSocket APIs

Frontend

JavaScript, HTML5, CSS3, responsive and accessible interfaces

Infrastructure

Linux, Apache, Nginx, Postfix, TLS, DNS, Cloudflare, VPS and colocation

Integrations

Payment gateways, blockchain APIs, public register APIs, webhooks

Real-time

WebSockets, Socket.io, event streaming, scheduled ingestion pipelines