about · the long version
I build things: web products people actually pay through, and the systems under Roblox games. Away from the desk I'm outside, ideally somewhere with a waterfall. At the desk there's Chopin or afro house in my ears.
I design a product and then build it: the public site, the booking flow, the dashboard behind it. React and TypeScript up front, Postgres and Supabase underneath.
Multiplayer systems under Roblox games: saves that survive a crash, networking the server stays in charge of, and economies nobody can exploit. All of it tested.
Software engineering at International Burch University in Sarajevo. Enrolled in 2024, graduated on June 25, 2026, halfway through an internship.
| COURSE | WHERE IT SHOWS UP |
|---|---|
| Data Structures & Algorithms | cutting per-frame physics work: 58 simple colliders instead of 269 ship parts |
| Databases | the reservation system behind Una Adventure's 130+ bookings |
| Web Programming | every React/TypeScript product I've shipped |
| Software Engineering | PRDs, ADRs and 60+ logged decisions on Fish or Die |
| Networks | server-authoritative multiplayer with range, rate and ownership checks |
| Operating Systems | session locking, so two servers never write the same save |
| Software Quality Assurance | ~45 headless test suites on Odyssey |
| Continuous Delivery & DevOps | Git/Rojo pipelines, lint and format gates, strict type checks |
| Functional Programming | pure, idempotent transactional writes for player data |
| UI/UX | a 93-module UI system, and designing Crochê and Una from scratch |
In games the client asks and the server checks range, rate and ownership before anything happens. On the web, same idea: the database is the truth, the UI is a view of it.
Anything I take over moves into a real workflow before new features: version control, strict types, a linter and tests. It costs a week at the start and saves a lot more than that later.
Balance questions and edge cases get a script, not an opinion. A simulation once showed only ~9% of perfect players could clear a game we were building, so we changed the design.
PRDs, decision logs, ADRs. Whoever works on the project next, me included, should be able to see why it was built that way.
I design the product and then build it, so nothing gets lost between a mockup and the thing people use.
I use Claude Code and MCP for inspecting, planning and implementing, and I review everything it touches. I'm the one who answers for the commit.
What I listen to while I work: classical, mostly Chopin, or afro house, mostly Afronom and Meliora. Either one keeps me focused for hours.
↑ that meter is the most accurate thing on this site
Before the desk took over, I worked outside.
I was a nature guide, taking people to places most of them had only seen in photos. My last job out there was waterfall jumper, which is a real job.
I did high diving too. You prepare properly and then you commit, because hesitating halfway is how people get hurt.
My favourite composer is Chopin. My favourite afro house DJs are Afronom and Meliora. I see no contradiction.
tip 1 of 10 · the playlist
Message me about a project, a job, or music you think I'd like.
