SAHMAN COMPUTING SYSTEMCHAPTER 01 / LOGIC
BIOGRAPHY PROCESSOREXPERIENCE → SYSTEM
01
INPUTCURIOSITY
02
STRUCTUREDISCIPLINE
03
CONTEXTPEOPLE
04
OUTPUTPRODUCT
MILITARY14 YEARS
COACHING20+ YEARS
SOFTWARE4+ YEARS
SYSTEM PRINCIPLE

Different careers, same pattern: understand the situation, build structure, test it against reality and improve it.

1958 / LOGIC / HOW I THINK

BEFORE CODE,
THERE WAS
LOGIC.

This is not a literal timeline. Each chapter borrows the visual language of a computing era to tell a different part of my story. My route into software was not a straight line. It passed through security studies, fourteen years of military service, decades of coaching and a constant interest in how systems behave.

Coding came later. The underlying habit was already there: understand the problem, separate signal from noise and turn complexity into something usable.

FOUNDATIONSecurity, systems and context
DISCIPLINE14 years of military service
PEOPLE20+ years of coaching
LOGICDISCIPLINE

My path did not start with software. It started with structure, responsibility and learning how to operate inside real systems.

SAHMAN DOS / PERSONAL HISTORYCHAPTER 02 / DISCIPLINE
1981 / COMMAND / DISCIPLINE

STRUCTURE
BEFORE
CODE.

Fourteen years in the military taught me discipline, responsibility, teamwork and how to work inside systems where details matter.

The terminal below turns that background into commands. It is less about nostalgia and more about the operating system I brought with me into development.

SAHMAN DOS 1.0PERSONAL SYSTEM
C:\> whoami
NAMEIRFAN ŠAHMAN
ROLEFULL-STACK DEVELOPER
MODEPRODUCT BUILDER
BACKGROUNDMILITARY / COACHING / SYSTEMS
INTERESTSOFTWARE / BLOCKCHAIN / MARKETS
LOCATIONSARAJEVO / REMOTE

I work best where product, frontend, backend and real-world constraints overlap.

C:\>
DISCIPLINEPEOPLE

Structure matters, but systems only become useful when they work for people. Coaching taught me that part.

1995 / PEOPLE / WHAT COACHING TAUGHT ME

SYSTEMS
HAVE TO WORK
FOR PEOPLE.

Long before I built interfaces, coaching taught me the same lesson: a technically correct plan is useless if the person cannot understand it, follow it or adapt it to real life.

Two decades of working with people shaped how I think about software today: clarity, feedback, progression and the next useful action matter as much as the machinery underneath.

SAHMAN OS 95GRAPHICAL USER INTERFACE
PROJECTS
_□×
File   Edit   View   Help
▰
MojTrener.baSPORTS MARKETPLACE
LIVE
▰
MojTrener OnlineCOACHING SAAS
BETA
▰
Nomad PointRENTAL PLATFORM
LIVE
▰
Limitless ElectroCLIENT WEBSITE
ACTIVE
◆ STARTPROJECTS
PEOPLECURIOSITY

Working with people led to a wider curiosity about technology, the web, security, blockchain, markets and the systems behind them.

1999 / CURIOSITY / WEB + MARKETS

CURIOSITY
MOVED
ONLINE.

The web opened a much larger system to explore: software, cybersecurity, search, blockchain, crypto markets and the behaviour connecting technology with people.

That curiosity eventually changed from observing systems to building them. Search, performance, distributed technology and market structure all became different ways of asking the same question: what is actually happening underneath?

SAHMAN DEVELOPMENT NETWORK

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
© 1999 SAHMAN DEVELOPMENT NETWORK · BEST VIEWED WITH A REAL BROWSER
CURIOSITYSYSTEM

Eventually curiosity stopped being something I only studied. I wanted to build the systems myself.

2015 / SYSTEM / HOW I BUILD

CURIOSITY
BECAME
CODE.

Full-stack development gave me a way to turn years of systems thinking into something concrete: interfaces, APIs, databases, authentication, caching, monitoring and mobile clients.

This is the part I enjoy most: understanding how the pieces fit together and how technical decisions affect the person using the product, the business behind it and the system in production.

SYSTEM ARCHITECTURECONNECTED PRODUCT
WEBNEXT.JS
↓
ACCESSAUTH
LOGICAPI
↓
DATA LAYERPRISMA
↓
DATABASEPOSTGRESQL
↓
CACHEREDIS
MONITORSENTRY
CLIENTMOBILE
CURRENT TOOLKITPRODUCT → PRODUCTION
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

WORKFLOW

The implementation changes. The process is more stable.

01DISCIPLINE

Military experience: structure, responsibility and execution.

02PEOPLE

Coaching experience: behaviour, feedback and adaptation.

03ANALYZE

Markets and systems: separate signal, incentives and risk.

04BUILD

Turn the model into working software.

05SHIP

Put it in front of real users and real production conditions.

06IMPROVE

Use evidence instead of assumptions for the next iteration.

SYSTEMPRODUCT

Code became the implementation layer. Product work connected everything before it: discipline, people, analysis, systems and ownership.

SAHMAN.DEVAVAILABLE / REMOTE
2026 / PRODUCTSARAJEVO / REMOTE

I BUILD
PRODUCTS
FROM IDEA TO
PRODUCTION.

Fourteen years of military discipline, more than two decades of coaching, a long interest in technology and markets, and now full-stack development — all converging in work I can carry from idea to production.

DISCIPLINEPEOPLESYSTEMSFULL-STACKPRODUCT
EXPLORE THE WORK ↓
00 / THE PATH

The portfolio is the current output. This is the system that produced it.

0114 YEARS / MILITARY
DISCIPLINE

Fourteen years of military service taught me structure, responsibility, teamwork and how to keep moving when the situation is not perfectly defined.

01
0220+ YEARS / COACHING
PEOPLE

Fitness and coaching taught me to work with real people, real constraints, feedback, behaviour and long-term progress instead of ideal scenarios.

02
03SECURITY & PEACE STUDIES
SECURITY

My academic background in security and peace studies strengthened the way I think about systems, risk, context and consequences.

03
04CRYPTO / BLOCKCHAIN
MARKETS

Crypto and blockchain became another systems laboratory: distributed technology, incentives, technical structure, fundamentals and crowd behaviour.

04
054+ YEARS / FULL-STACK
SOFTWARE

Coding turned that systems mindset into software across frontend, backend, databases, infrastructure, mobile workflows and technical SEO.

05
06MOJTRENER / PRODUCT
FOUNDER

Building MojTrener moved me from implementing features to owning the whole loop: idea, product decisions, users, production, analytics and iteration.

06
01 / REAL WORK

Products and client work I built, launched or actively work on.

01SPORTS MARKETPLACE

MojTrener.ba

A production marketplace for discovering trainers through sports, cities, structured profiles and location-aware discovery.

ROLEFounder / Product / Full-stack
Next.jsTypeScriptPrismaSupabaseRedis
LIVE
LIVE ↗
MojTrener.ba screenshot
02COACHING SAAS

MojTrener Online

A coaching platform connecting trainers and clients through programs, workouts, progress, recovery, nutrition and day-to-day coaching workflows.

ROLEFounder / Product / Full-stack
Next.jsTypeScriptPrismaPostgreSQLAuth
BETA
MojTrener Online screenshot
03RENTAL PLATFORM

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
LIVE ↗
Nomad Point screenshot
04CLIENT WEBSITE

Limitless Electro

A custom website built from scratch for an electrical services company in Sarajevo, focused on clear service presentation, trust and straightforward customer enquiries.

ROLEWeb Design / Development
Next.jsTypeScriptTechnical SEO
ACTIVE
Limitless Electro screenshot
02 / HOW I WORK

BUILD.
SHIP.
IMPROVE.

I prefer real production problems to hypothetical ones.

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.

03 / NEXT

WHAT DO
WE BUILD
NEXT?

Open to remote development roles, product teams and selected collaborations.

Send me an email ↗
SAHMAN.DEVLOGIC → DISCIPLINE → PEOPLE → CURIOSITY → SYSTEM → PRODUCT© 2026 IRFAN ŠAHMAN