larprober logo, an ink bottle with three strokes rising from it larprober

Taking new projects  Türkiye, GMT+3

I build small software that keeps working after I hand it over.

Freelance developer. Desktop applications, Android applications, command line tools, websites and small servers, usually with no dependencies at all, so what you get still builds in two years.

Reply within 24 hours on weekdays. Fixed quote before any work starts. You keep the source.

0
runtime dependencies in the tools on this page
80
games inside one 224 KB Android app
82
security tools in a Linux image I build and verify
4M
hands simulated to prove one card engine

01  What I build

Six things I do properly.

How each one works

  • 01

    Desktop applications

    Installers and portable executables that run on a machine with nothing installed on it. Real windows, real file handling, no browser tab pretending to be an app.

    Windows, packaged
  • 02

    Android applications

    Signed APKs, background services that survive the battery optimiser, and the honest conversation about what the platform will and will not let an app do.

    Kotlin or WebView
  • 03

    Command line tools

    Scanners, linters, generators and converters that install with one command and keep working, because there is no dependency tree underneath them to rot.

    Node, zero dependencies
  • 04

    Websites and portfolios

    Hand built pages with real metadata, a sitemap, a custom error page and no framework tax. This site is an example of the output.

    Static, fast, indexable
  • 05

    Small servers and bots

    HTTP APIs, long polling, signalling servers and chat bots. Small enough to read in an afternoon and cheap enough to host on anything.

    Node, Kotlin, Discord
  • 06

    Security and analysis tooling

    Vulnerability scanners, malware triage and static analysis. Tools that name what they found instead of returning a number you cannot act on.

    Scanners, log tools

03  How it works

Four steps, no surprises in the middle.

  • 01

    Scope

    A short back and forth until the thing you want fits in one paragraph that we both agree on. This is free and it is where most of the risk gets removed.

  • 02

    Quote

    One fixed price and one delivery date. If the scope changes later, the quote changes in the open, before the work happens.

  • 03

    Build

    You get something runnable early and often. No single reveal at the end, because that is how projects end up wrong in a way nobody noticed for a month.

  • 04

    Handover

    Full source, build instructions that were followed on a clean machine, and a walkthrough. Nothing about the delivery ties you to me.

04  Questions

The six things everyone asks first.

Still unanswered? Ask directly.

What does a project cost?

A fixed price, quoted after a short scope conversation, so you know the number before any work starts. Small tools land in a day or two. An application with a server behind it takes longer, and the quote says how long.

Do I get the source code?

Yes, always, along with build instructions that have been run on a clean machine. Once the invoice is paid the work is yours. Nothing is hosted on my account, and there is no part of the delivery that only I can rebuild.

What happens if it breaks after handover?

If it does not do what the agreed scope said it would, I fix it and you pay nothing. New behaviour that was never in the scope is quoted as new work. That line is written into the quote so neither of us has to guess later.

Can you work on a codebase that already exists?

Yes. Send the repository or a description of it. Most of my own tools were built to read other people’s code, so reading yours is the normal starting point rather than a favour.

Which platforms do you build for?

Windows desktop, Android, command line on any system that runs Node, static sites, and small servers in Node or Kotlin. Not iOS: that needs a Mac and a paid developer account, and I would rather say so than take the job and learn on your budget.

How do we start?

Send the form on the contact page with a paragraph about what you need. You get a reply within 24 hours on weekdays, with either a plan and a quote or a straight answer that this is outside what I do well.

Tell me what you need built.

One paragraph is enough to start. If it is not something I can do well, I will say so instead of taking the work.

Start a project

Reply within 24 hours on weekdays. Taking new projects.

Taking new projectsReply in 24 hours on weekdays Start a project