Skip to content
yangetze
ESLet's talk

About me

Two formal jobs in ten years, plus successful standalone projects. I don't leave things unfinished. I model the minimum system that solves 80% of a problem with 20% of the effort. Not every problem needs code — sometimes the right fix is a process.

Systems Engineer & Software Developer · Venezuela

The context is the work

Most people ask AI for code. I maintain the context that makes the answer right.

I keep a versioned technical memory — what I've built, which tools I actually know and how well, and why I picked one over another. Each project carries its own design memory: rules written in the negative, born from mistakes that already happened, so they don't happen twice.

One of those rules exists because a replyTo in camelCase took down production. The SDK wanted reply_to. With auto-deploy, a type error in a route handler isn't a runtime error — it's downtime.

~/ibe/CLAUDE.md · design memory
Rules written in the negative — born from real mistakes
✗ Don't revert the footer to 4 columns.
✗ Don't fabricate content when the YouTube API
doesn't respond. Show the honest fallback.
✗ replyTo → reply_to. The SDK uses snake_case.
(jul-28: broke the production build)