How a piece of work goes

4 steps · 3 worktrees

one feature · main + 3 worktreespick a worktree
  1. me

    01Rules first

    Written in the repo, read every session.

  2. me

    02Then the spec

    Before any code, in writing.

  3. agent

    03Agents write the code

    Each in its own worktree, with its tests.

  4. me

    04Review

    Before anything goes back to main.

wt/ui doesn't go back to main before review

What gets a yes, what gets a no

Vibe coding gets you an MVP. Past that, you need standards.

  1. NoRambling at the agent, then "you handle it".

    YesStarting with the technical picture: the data model, the boundaries, what done means.

  2. NoAn agent that puts DTOs and mappings somewhere new each time.

    YesWritten rules: where controllers, services, DTOs and mappings live, and why there.

  3. NoAn agent that starts from zero every session.

    YesMemory lives in the repo: decisions, patterns, reference code.

  4. NoMistaking "it works" for "it's done".

    YesNothing closes before security, scale and maintenance get a look.

Products

5 live · 1 building

HookSense screenshot

HookSense

live

Webhooks your AI agents can wait on. Instead of polling, it opens a callback URL and waits for the result.

8 OctScrolling webhook sources landed on the landing page.

Yayınlıyor screenshot

Yayınlıyor

live

Where Turkish serial fiction lives. 259K reads, 2K readers.

14 OctThe page slid sideways on iPhone. Fixed.

Cordy screenshot

Cordy

client work

A reading app, shipped to both stores.

SelfInbox screenshot

SelfInbox

live

Self-hosted email on your own domain. Open source.

2 NovFixed the verification link and catch-all replies. Resend errors show up now too.

UptimeCrow screenshot

UptimeCrow

live

Open-source uptime monitoring & status pages.

12 SepOne wrong WEB_ROOT took every page down. Not anymore.

Lumecrawl screenshot

Lumecrawl

building

Does AI recommend your business? Checks whether sites show up in AI answers.

2 NovStopped selling access control and turned to weekly AI visibility tracking. The free report comes first now.

Tools

on GitHub · 5

system-design-canvasFor drawing the architecture before writing the code.hooksense-mcpNo wasted tokens on long jobs. It wakes up when the webhook arrives.lambda-doctorFinds out why your Lambda wakes up slowly.sidebandFor controlling an external display from the menu bar.whyportWhy a port is open, who's using it, and one click to stop it. In the macOS menu bar.

Recent work

September – November 2026

November

  • Lumecrawl. Stopped selling access control and turned to weekly AI visibility tracking. The free report comes first now.

  • SelfInbox. Fixed the verification link and catch-all replies. Resend errors show up now too.

October

  • Yayınlıyor. The page slid sideways on iPhone. Fixed.

  • HookSense. Scrolling webhook sources landed on the landing page.

  • hooksense-mcp. The MCP tools had fallen behind the API. Caught them up.

September

  • System Design Canvas. New look, and auto layout crosses fewer lines.

  • UptimeCrow. One wrong WEB_ROOT took every page down. Not anymore.

Writing

soon

Poking at Jev right now. A post about it is coming.

Designing a real-time stock control system on AWS Lambda

How we kept inventory accurate across 23 airport duty-free stores with a serverless event-driven backend — and the trade-offs that came with it.

Let's look at something together

If you have a working MVP but every deploy breaks something, or it grew fast and every change breaks something else, let's talk for 15 minutes.

or [email protected]

Open the calendarThe calendar opens in a new tab with your sentence added to the booking note.