Start a project

From CPU instruction to finished product. I work in assembly, C++ and CUDA on software that has to be fast and can't afford to fail. I also build the websites and automation around it, so you end up with something people can actually use.

What brings people to me

You don't need to know what a cache or assembly is. Tell me what's getting in the way, and finding the cause is my job.

Your software is slow, and more hardware stopped helping.

I find where the time actually goes and speed up that part. Rewriting everything is rarely necessary.

Your cloud bill is growing faster than your business.

I optimize the code so the same work needs less compute, and you pay for less of it.

It crashes, and nobody can say why.

I trace the failure to its real cause and fix that, so it doesn't come back next month.

Your computations take hours, and you need answers today.

I move the heavy work onto GPUs with CUDA and get the most out of your CPUs.

You need a website or a bot, or you're tired of doing it by hand.

I build fast websites, Telegram bots and automation that keep running without supervision.

Knitted breakdown of the instruction 48 89 E5

How we'd work together

You always know what's happening, how long it will take and what you're paying for.

  1. Request

    Describe the problem in your own words. Technical details are optional.

  2. Diagnosis

    I work out what's really going on and explain it in plain language, with a plan, a timeline and a price.

  3. Work

    I follow the plan and keep you posted. If anything changes, you hear about it right away.

  4. Handover

    You get the finished result, before-and-after numbers, and code you can maintain without me.

The whole chain, end to end

Low-level engineering

  • Architecture and audits of existing code
  • Optimization in assembly and C++
  • GPU computing with CUDA
Start a project

Websites

  • Landing pages and sites that load fast
  • Forms that deliver every request
  • Light and dark themes, built for phones too
Start a project

Automation

  • Telegram bots and background services
  • Scripts that replace manual routine
  • Connecting services through their APIs
Start a project

Common questions

Do I need to understand the technical details?

No. Describe the problem the way you'd describe it to a colleague. I'll ask for whatever else I need and explain my findings in plain language.

How much does it cost?

It depends on the problem. After the diagnosis you get a plan and a price, and you decide whether to go ahead.

What if it can't be made faster?

I'll tell you as soon as I know, explain why, and lay out the options you still have. I don't promise results I can't stand behind.

Is my code safe with you?

Everything you share stays yours. I only ask for the access the job needs and use your materials for nothing else. I'm happy to sign an NDA.

Do you work on code you didn't write?

Yes, most of the time. Old and undocumented code is normal for this kind of work.

What happens after handover?

If a bug turns up in my work, I treat it as mine. You also get code you can build and maintain without depending on me.

Knitted table of chapter numbers with the section sign circled

My Constitution

Instead of an about page: what I value in my work, what I promise, and what I'll refuse even if you pay me for it.