TODO — the one line that sells you. Name the problem you solve and who for. Example: 'I make slow Rails applications fast for Series-A teams.' Avoid 'passionate software engineer'.
Ways we can work together. Every engagement starts with a short call to check the fit — no pitch deck, no pressure.
TODO — a fixed-scope review of a slow or expensive system, ending in a prioritised plan you can act on with or without me.
TODO — I join your team part-time to raise the technical bar: shipping features, reviewing code, and mentoring the engineers you already have.
TODO — from empty repository to production. Best for teams who need a solid foundation laid quickly and correctly.
TODO — a recurring call for founders and teams who need a senior engineer to think out loud with before making expensive decisions.
Selected engagements. Each one lists what changed as a result — the numbers matter more than the tech stack.
Design and build
A statically generated brand hub that ships almost no JavaScript and is maintained by editing plain text files.
Talks, walkthroughs, and build logs — the fastest way to see how I think through a problem.
12:04 TODO — one or two sentences on what a viewer gets out of this. Delete these three placeholder entries once you add real videos; the Videos section hides itself automatically when this file is empty.
8:41 TODO — drop the `thumbnail` field entirely for YouTube videos and the real thumbnail is derived from the URL automatically.
31:15 TODO — set `platform` to "conference" or "twitch" for non-YouTube content, and supply your own `thumbnail` path for those.
Tell me what you're working on and what's in the way. If I'm not the right person for it, I'll say so — and point you at someone who is.
hello@jesusrtech.com