MojTrener.ba
A production marketplace for discovering trainers through sports, cities, structured profiles and location-aware discovery.
ROLEFounder / Product / Full-stack
Next.jsTypeScriptPrismaSupabaseRedis
LIVE
PROCESSING UNITPROBLEM → PRODUCT
01
INPUTPROBLEM02
CONTEXTUNDERSTAND03
STRUCTURESYSTEM04
OUTPUTPRODUCTLOGICONLINE
CONTEXTREADY
OUTPUTREADY
SYSTEM PRINCIPLE
Complexity becomes useful only after it becomes understandable.
1958 / HOW I THINKBEFORE
BEFORE
INTERFACES,
THERE WAS
LOGIC.
Every product starts before the interface. There is a problem, context around it and a set of decisions that turn that problem into structure.
That is still the way I approach software today: understand what actually needs to happen before deciding what the screen should look like.
INPUTReal problemPROCESSUnderstand the systemOUTPUTSomething people can use
LOGICCOMMAND
Once machines could process logic, the next challenge was telling them what to do.
1981 / WHO I AMSOFTWARE
SOFTWARE
LEARNED TO
LISTEN.
The command line turned intent into instructions. So this chapter does the same thing: ask the system something about me.
SAHMAN DOS 1.0640K MEMORY
C:\> whoami
NAMEIRFAN ŠAHMAN
ROLEFULL-STACK DEVELOPER
MODEPRODUCT BUILDER
LOCATIONSARAJEVO / REMOTE
I work best where product, frontend and backend overlap.
C:\>
COMMANDINTERFACE
Commands worked. Interfaces made software understandable to everyone else.
1995 / WHAT I BUILTCOMPUTERS
COMPUTERS
STOPPED ASKING
FOR COMMANDS.
Interfaces changed who could use software. Functionality still mattered, but now the system also had to explain itself.
That is why product work is not only code. Structure, hierarchy and the next action matter just as much.
_□×
▰
MojTrener.baSPORTS MARKETPLACE
LIVE▰
MojTrener OnlineCOACHING SAAS
BETA▰
Nomad PointRENTAL PLATFORM
LIVE▰
Limitless ElectroCOMMERCE REBUILD
BUILDINGINTERFACEWEB
Then software escaped the machine. A URL became enough to reach the world.
1999 / HOW PRODUCTS GET FOUNDTHEN SOFTWARE
THEN SOFTWARE
LEFT THE
COMPUTER.
The web made software distributable. Suddenly a product could reach anyone with a browser.
That also introduced a new problem: building something useful is not enough if nobody can find it, trust it or use it quickly.
THE WEB IS PART OF THE PRODUCT
Search · Performance · Discovery · Clarity
DISCOVERY.HTML
If nobody finds the product, the product has another problem.
I started thinking about search and acquisition as part of development rather than something added after launch.
SEARCHIntent before keywords
STRUCTUREPages that reflect how people actually search
DISCOVERYProduct architecture and SEO working together
CONVERSIONFinding the product is only the first step
WEBSYSTEM
Websites stopped being pages. They became connected products with data, APIs and infrastructure.
2015 / HOW I BUILDTHE WEBSITE
THE WEBSITE
BECAME A
SYSTEM.
Modern products stopped being collections of pages. Authentication, data, APIs, caching, monitoring and mobile clients became one connected system.
This is the part of full-stack work I enjoy: understanding how those pieces fit together rather than treating each one as a separate world.
WEBNEXT.JS
↓
ACCESSAUTH
LOGICAPI
↓
DATA LAYERPRISMA
↓
DATABASEPOSTGRESQL
↓
CACHEREDIS
MONITORSENTRY
CLIENTMOBILE
01
FRONTEND
Next.js / React / TypeScript / Tailwind
02
BACKEND
Prisma / PostgreSQL / API routes / Authentication
03
INFRA
Vercel / Redis / Sentry / Analytics
04
MOBILE
React Native / Expo / Notifications / Camera workflows
The implementation changes. The process is more stable.
01UNDERSTAND
What problem are we actually solving?
02DESIGN
What data and relationships does the system need?
03BUILD
Create the smallest complete version that works.
04SHIP
Put it in front of real users.
05MEASURE
Observe behaviour, failures and acquisition.
06IMPROVE
Use reality instead of assumptions for the next iteration.
SYSTEMPRODUCT
The tools are only the implementation. The final question is whether the product actually works for real people.
I BUILD
PRODUCTS
FROM IDEA TO
PRODUCTION.
Full-stack developer and product builder working across interface, application logic, data, infrastructure, mobile, technical SEO and the decisions that connect them.
PRODUCTFULL-STACKMOBILEDISCOVERY
EXPLORE THE WORK↓Products I built, launched or actively work on.
MojTrener Online
A coaching platform connecting trainers and clients through programs, workouts, progress, recovery, nutrition and mobile workflows.
ROLEProduct / Full-stack / Mobile
Next.jsReact NativePrismaPostgreSQL
BETA
Nomad Point
A car-rental platform where development extends into local search architecture, technical SEO and clearer conversion paths.
ROLEDevelopment / Technical SEO
Next.jsTypeScriptSEOVercel
LIVE
Limitless Electro
A new Next.js implementation replacing an older WordPress foundation with cleaner architecture and room for future commerce features.
ROLEArchitecture / Development
Next.jsTypeScriptCommerceTechnical SEO
BUILDING
The work does not stop when a site goes live.
MojTrener OnlinePrograms workflow
Duplicate program, safer delete flow and client relationship checks.
Nomad PointSearch architecture
Local intent, Sarajevo/Tuzla structure and airport-focused landing strategy.
Limitless ElectroNext.js rebuild
New project foundation, App Router and architecture planning.
MojTrener.baProduction iteration
Privacy controls, location handling and technical SEO work.
BUILD.
SHIP.
IMPROVE.
I prefer production problems over portfolio problems.
Real users expose the things mockups cannot: unclear flows, performance issues, incorrect assumptions and missing product decisions.
I like understanding the complete system: interface, data, application logic, infrastructure, privacy, analytics and acquisition.
WHAT DO
WE BUILD
NEXT?
Open to remote development roles, product teams and selected collaborations.
hello@sahman.dev↗