What I get hired for

Fixing Live Systems

Something live is broken or scary to touch. I fix it with proof, behind a tagged rollback.

Proof
3 pieces of work
Tools
Playwright, Docker, PostgreSQL
Availability
Remote · UTC+7
Reply
Within a day
01Proof

Where this has already shipped.

9,800 stuck emails traced to the provider. Open any of the three to read how it was built.

Playwright · Docker · PostgreSQL · MongoDB · Shopify CLI · Git tagged rollbacks

02Brief

Build your brief.

Tick the parts that sound like your project. They collect in a bar at the bottom of the page, and one button turns them into an email to me. Nothing is sent until you press it.

  • Diagnose a live bug

    The cause found from logs and evidence rather than guessing, on a system that has real users.

  • Deploy behind a tagged rollback

    A fix shipped with the previous version kept ready, so reverting is one command and not a rebuild.

  • Stuck or missing emails

    Message state traced at the provider before any of your own sending code is rewritten.

  • A page that is too slow

    The explain plan run first, then the payload or the index fixed, whichever is the real problem.

  • Login and session bugs

    A login redirect bug found by untangling the theme code, and mid-session logouts found by reading the access logs by timestamp.

  • End-to-end verification

    Every change tested through a real browser before it counts as done.

03Field notes

What I already knew about your domain.

The traps specific to this kind of product, each one from work that shipped rather than from a reading list.

04Start

Think this is your problem?

Tell me what is happening in your own words. No brief needed, no spec. I will tell you within a day whether it is mine to solve, and roughly what it takes.

Describe the problemrafiimanggala3@gmail.com · reply within a day