AboutAdmir Šaheta · Sarajevo, BiH

Nobody sees the work.Everybody feels it.

I'm Admir — a platform engineer with an unreasonable love for technology, good design, and merak.

StackTypeScript, Go, Rust, Swift, Kotlin (dark times prerequired), React/Yew
Open source141 repositories
BaseSarajevo, BiH
Admir Šaheta
01 — HedonismSomething cold in a glass. Merak, on purpose.
02 — Hedonism × WorkSame sunset, terminal open. The commits can't tell the difference.
01 — What the job actually is

Platform as a product.

The mark is matter, not a surface. Same goes for the systems underneath it.

I started with Swift and UIKit, took the scenic route through Android and backend engineering, and eventually ended up where I belong: building the layers underneath everything else.

At Shopify, I worked on public JavaScript and TypeScript tooling, the shopify-js-sdk, and the Remix v2 → React Router 7 transition. Now I build platform infrastructure and agentic systems at FlyRank.

SDK contracts. Service boundaries. Build systems. Developer tooling. The wonderfully unglamorous machinery that makes everything else possible.

The stack above is a toolbox, not an identity — swap the language and the job stays the same. A carpenter doesn't care whether it's a hand plane or a router, as long as the cut comes out true; I don't care whether it's TypeScript or Rust, as long as the boundary holds and the contract is honest.

I take the work seriously. Myself, less so.

There is, after all, more to life than shipping software. Occasionally there is the Adriatic, a sailboat, something cold in a glass, and merak. I call it work-life balance. One Aperol a day keeps the burnout away.

02 — What I care about

Four rules I don't bend.

03 — In the open

Read by people I'll never meet.

Public repositories, public API surfaces, public mistakes. Writing code other engineers depend on changes how you write it — you stop optimising for the commit and start optimising for the person reading it in two years.

github.com/admirsaheta
0Public repositories · exact, from snapshot
04 — Writing

I write about the decisions, not the demos.

Long-form, not list-posts — the kind of writing I do when a decision took long enough to reason through that it's worth keeping. Where a service should end, what an SDK promises the moment it ships, why a build went slow and what it cost to make it fast again. If you're hiring for someone who thinks this way about the parts nobody sees, that's the whole pitch.