THE STUDIO
Our second product.
Every project leaves two results: the software, and the company that builds the next one. This page is about the second result — who works here, how the place is put together, and how it keeps getting better.
How the company is put together
There are no fixed teams. Each project is staffed to its size and complexity, and the people who come to understand a problem usually see it through. But continuity is not allowed to depend on that: standards, documentation, review and tooling exist so that what one project teaches belongs to the company — not to whoever learned it first.
Titles here describe responsibility, not rank. Three technical leads hold direction across our projects, one design lead does the same for everything we ship, and everyone builds. The company is still small enough that everyone knows what everyone else is working on — and it is growing deliberately, so that stays a property of how we work rather than of headcount.
The standards came from the founder, who still writes and reviews code. They are written down, argued about, and revised — so they belong to the company, not to him.
- STAFFING
- Sized to the project
- WHO BUILDS IT
- The people below — nothing outsourced
- STUDIO
- Gornji Vakuf-Uskoplje, BiH
“Tools change. Responsibility doesn't.”
ON TOOLS, INCLUDING AI
How people grow here
Nobody here is expected to know everything. Everyone is expected to keep getting better — learning is treated as part of the job, not something that happens after it. Hiring is slow for the same reason: each person who joins has to raise what the company is capable of, not just its headcount.
Most of that growth happens in the work itself. Review is where standards move between people; when something proves itself, it gets written down or built into tooling so the whole company gets better at once, and stays better.
WHERE AI FITS
AI runs through everything we build — scaffolding, tests, migrations, the repetitive middle of the work. What it doesn't do is decide what to build, or whether the result is correct. Those stay with the engineer responsible.
That's what the line above means in practice. AI is the current tool; it won't be the last, and we expect to adopt whatever replaces it. What doesn't change is who answers for the work: an engineer who understood the problem, made the decisions, and verified the result.
The roster
LEADS FIRST, THEN ENGINEERS
Amar Idrizović
TECHNICAL LEAD
Believes good engineering starts with understanding the problem, not the solution.
Emira Huskić
DESIGN LEAD
Designs products that feel natural long before they feel beautiful.
Selma Hadžijusufović
TECHNICAL LEAD
Equally comfortable leading the product, the team, or the implementation.
Zlatan Dadić
TECHNICAL LEAD
Knows the right question is often more valuable than the first answer.
Nedim Kevro
SOFTWARE ENGINEER
Brings patience to difficult problems and consistency to everyday work.
Nedim Muminović
SOFTWARE ENGINEER
Usually the first to ask whether the simpler solution might also be the better one.
Midhat Drino
SOFTWARE ENGINEER
Usually goes one step further than what was originally asked.
Josip Knežević
SOFTWARE ENGINEER
Never stops learning, and quietly raises the standard with every project.
Jakov Vuković
SOFTWARE ENGINEER
Enjoys turning complex ideas into software people can actually use.
Amel Kamber
SOFTWARE ENGINEER
The kind of engineer who doesn't get intimidated by difficult tasks.
These are the people who would build it.
The first conversation is about scope, cost, trade-offs and fit.