I'm a developer who genuinely enjoys building complete tools from start to finish. Not just copying tutorial snippets where everything works on the first try, but building real systems where data gets messy, edge cases bite, and you have to think through what happens when a network drops or a user clicks the wrong button.

I've been building and shipping since 2024—balancing freelance client work, internships, and a full-time remote role with finishing my CS degree at St. Mary's University.

I actually started out in UI/UX design at RDXDelta. I spent months obsessing over spacing tokens, color contrast, and component states in Figma. But the more interfaces I built, the more I noticed a frustrating pattern: even the cleanest design feels terrible if the backend is slow, the database queries crawl, or the API returns random 500 errors. That's what pulled me into backend development, databases, and system architecture. I wanted to understand the whole machine, not just paint the bodywork.

Living and coding in Addis Ababa also taught me to respect real-world constraints. When I built Dailybirr, I chose Telegram because asking day laborers to download a 60MB app on metered mobile data was a non-starter. When I worked on HCMS at Wawmox, clinic staff didn't care about flashy animations—they needed a queue system that wouldn't lose patient vitals and an appointment calendar that handled Ethiopian date calculations. I wrote 180+ tests for it because medical records can't tolerate guesswork.

Over time, my mindset has shifted from “can I get this to work?” to “will this be clear, stable, and easy to debug six months from now?” Between building production features, diving into algorithms with A2SV, and studying Computer Science and Mathematics at St. Mary's, I spend most of my time building, breaking things, and figuring out how they work under the hood.