
Low-level engineering
- Architecture and audits of existing code
- Optimization in assembly and C++
- GPU computing with CUDA
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.
I find where the time actually goes and speed up that part. Rewriting everything is rarely necessary.
I optimize the code so the same work needs less compute, and you pay for less of it.
I trace the failure to its real cause and fix that, so it doesn't come back next month.
I move the heavy work onto GPUs with CUDA and get the most out of your CPUs.
I build fast websites, Telegram bots and automation that keep running without supervision.

You always know what's happening, how long it will take and what you're paying for.
Describe the problem in your own words. Technical details are optional.
I work out what's really going on and explain it in plain language, with a plan, a timeline and a price.
I follow the plan and keep you posted. If anything changes, you hear about it right away.
You get the finished result, before-and-after numbers, and code you can maintain without me.



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.
It depends on the problem. After the diagnosis you get a plan and a price, and you decide whether to go ahead.
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.
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.
Yes, most of the time. Old and undocumented code is normal for this kind of work.
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.


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.