Full-stack · QA background · one person
Nine products built end to end. The oldest has been live eleven months — on my monitoring, my backups, my phone number.
Passing the tests isn't the same as working.
Four ways to start, the five steps every project runs through, what I need from you — and where my limits are, said before the invoice.
Read the client page → For hiring teamsThe path from testing to building, the stack in full, how I prove a thing works — and the roles I'm honestly wrong for.
Read the hiring page →A client finds a specialist, books a session and pays up front. The money is held until the session actually takes place, then paid out automatically. Video calls, refunds, disputes, and an admin panel serving four kinds of user.
Animal profiles with photos and medical records, adoption applications, volunteer moderation, and messaging between the shelter and the families applying. Built for phones, because the work happens at the kennels — and kept running by me: monitoring, nightly backups, certificate renewals.
A web app for children of six to fifteen: they talk to an animal companion, take care lessons with quizzes and keep a virtual pet fed and well. Installs from the browser, no app store in the way.
A browser extension with tasks, a pomodoro timer, tab tidying and a chat assistant — plus a small pet in the corner that reacts to how the session is going. Its own backend behind it.
A platform that carries a dome home through its whole life: designed in 3D by the buyer, built by the maker, then rented, repaired and resold by its owner — under each manufacturer’s own brand.
Two hundred motorcycle models with their specifications, prices in two markets and the accessories that fit each one, set side by side. Every published figure traces back to the manufacturer's own sheet.
A site for a supplier of shelters, safe rooms, armoured steel and CBRN protection, selling into Qatar, the UAE and the Middle East. Enquiries land straight in the sales inbox, in English and Arabic.
A Virginia business that lends against, buys and repairs jewellery and watches. Sixty landing pages, each written for what people actually search and turning it into an enquiry. Deliberately not a shop.
Marketing site and admin panel for an investor group: pages, sections and photos edited by the owner — and even a move to a new web address handled from the panel instead of by a developer.
Payment providers routinely resend the same notification. Every payment message carries a key that makes a repeat impossible — and if that protection is ever removed, the build stops before release.
Testing tools happily count checks that never actually ran. Mine measure only what executed, and every figure I put in front of a client links to the run that produced it.
Automatic rebuilds are notorious for restoring outdated prices, products and placeholder details. Anything a person has confirmed is locked, and the machine is not allowed past it.
How every screen looks — including when it's empty, when something fails, and on an old phone in bright sun.
The part people see, the part behind it, and the admin panel the owner actually works in.
The stage solo builders skip. It's what I did professionally for five years, and it happens before a client ever sees a screen.
Onto a real address with a real certificate — and back to the previous version in minutes if it's ever needed.
Eleven months and counting on the oldest: watched, backed up, renewed. The only proof that counts.
Five years as a quality engineer, paid to find what breaks in other people's software. Then I started building my own products, and the habit came with me: work out how a thing can fail before building it, and never publish a number I can't stand behind.
Nine products since, all nine described above. Writing the code is about one hour in seven — the other six are why the result still works a year later.
The task, the deadline, and what state it's in. You'll get a straight answer on scope and timing in the first reply.
Prefer email? thuravchak@gmail.com