/ 02 about
→ the
person
behind it ←

I came to computers late, dropped out of college, and spent a good while not being particularly good at anything. A friend suggested I try software. That was the whole turning point.

Before that, I was drifting. After that, I had something to show up for. I don't think I'm naturally gifted — I just found the work that makes me feel like I'm in the right place, and I've been building ever since.

Six years in, I've shipped insurance platforms, pharmacy systems, logistics dashboards, component libraries, and a few things that don't fit a neat category. A lot of it has been in high-stakes Ethiopian enterprise — but that's context, not a constraint. I'll build whatever's worth building.

Stack
Vue.js React TypeScript Node.js Elixir Kotlin MySQL PostgreSQL etc.
I care about
Systems that hold up Teaching what I know Finishing things
I'm tired of
AI fear mongering A new JS package every week (I'm part of the problem 😅)
/ 03 services · what I do

Four things, done properly.

Pick one, or mix them
A.

Frontend apps — Vue or React

Dynamic, responsive UIs that actually perform. Component-driven from the start, so the codebase doesn't become a haunted house six months later.

Vue.js React TypeScript TanStack
B.

Component libraries & design systems

Custom, reusable component systems — tables, forms, modals — built for your exact use case, not for the npm average. Published one. Built several more that didn't ship to npm but should have.

design tokens headless UI form validation
C.

Healthcare & fintech UI

Complex domain, high stakes, zero room for confusing UX. I've built for hospitals and insurance companies — the kind of software where a confusing modal is actually a problem.

pharmacy systems insurance platforms claims UI
D.

Technical leadership

Code reviews, architecture decisions, onboarding new devs. I've led frontend teams and lived to tell the tale. I'll speak up when something is heading the wrong direction — before it becomes a problem, not after.

code review mentoring async-friendly
/ 04 process · how we'd work

Four steps, no surprises.

~ 4 to 10 weeks
01 / Understand ~ Week 0

Listen first.

30-minute call. I ask too many questions. You walk away with a written summary of what we agreed on, either way.

02 / Prototype ~ Week 1

Something clickable.

No wireframes, no Figma decks. A real prototype — you interact with it, you tell me what's wrong, we fix it.

03 / Build ~ Week 2 – 8

Ship in slices.

Weekly check-ins. Always deployable. You always know what's done and what's next — no black-hole sprints.

04 / Handoff ~ Final week

Hand it over.

Docs, walkthrough, two weeks async support. Then I get out of your way — the goal is that you never need me to explain your own codebase.

/ 05 words

What people would say.

written by me · no one was harmed
"

One of the best engineers I've worked with. Great instincts, clean code, ships on time. Genuinely impressive human being. I'd work with him again immediately. I am completely unbiased and this is a real quote.

A Real Colleague · Addis Ababa Completely unbiased
"

I wrote all of these. Every single one. This testimonial section is fabricated. But the work in the projects section is real, and the code on GitHub is real — so maybe just check that instead.

Abel · The Man Himself No shame whatsoever
/ work together

Like the look of it? Say hi.

Start a conversation