Why Sokkan Exists

I didn't pick the name Sokkan because it sounded unique. It comes from سکان (sokkān) — a ship's helm, in Persian. And once I found out what it meant, it felt like the name had been waiting to be used.

A helm is a small thing. You can't see it from the dock, and nobody watching a ship from the harbor is looking at it. But it's the one thing that decides where a ship that size actually ends up going. That's what I wanted to be — not the ship, not the destination, but the part that makes sure the direction actually gets reached.

I've been doing freelance work since 2019 — web apps, internal systems, automation, whatever clients needed at the time. For years, none of it had a name — it was just me and my laptop. What changed in 2026 wasn't the work itself, it was exactly the same — what changed is that I finally put a name on what I'd been doing all along.

The principle I've held onto since the start, and try to keep in every project: the ship belongs to the client, the destination is theirs to choose — I hold the technical helm. That means I'm not here to dictate where your business should go, but to make sure that whatever direction you choose, the system can actually get you there.

Three things I try to protect in every piece of work, born from that principle:

Control — clients should always hold full control over what I build. The code becomes yours once it's paid for, the system is something you can monitor yourself, nothing is hidden.

Precision — clear scope, honest estimates, and pricing that makes sense. I'd rather say "I'm not sure about this part yet" upfront than have a client caught off guard at the end.

Direction — technology is a means, not the point. I always ask "where are you trying to go" before I ask "what framework do you want to use."

Some of what I'm building under the Sokkan name — Flotilla, Knot, Buoy — mostly grew out of problems I ran into myself while doing client work over the years. I'll write about each of their reasons separately, because each one has its own story.

This journal is where I write all of it down — the decisions I make, the reasoning behind them, and the things I learn along the way. What I build, I document. Welcome.