Skip to main content

About

Furkan Namlı

Furkan Namlı

Developer in Istanbul. I ship more than one person used to be able to, and I keep a record of what that is actually worth once it has to stay up.

Agents made building cheap, and I took the offer. I shipped a 200,000-page catalogue alone, in months, on a stack I would not have attempted on my own time. Parts of it are the best work I have shipped: an ingest chain that reconciles four upstream sources, an edge cache that keeps anonymous traffic off the origin entirely, and a deploy that health-checks itself and rolls back without me.

Other parts arrived on their own schedule. A backup script that put the database on a public CDN, a caching flag that had been off since launch, a disk that filled until Postgres shut itself down, and one identity mistake that poisoned a catalogue four ways. None of it is a story about a model writing bad code. Every one is obvious the moment somebody reads the file.

Plenty of people write about getting an agent to produce code, and plenty more write about why it will not work. Both are cheap to write. What I have instead is a running system with a bill attached, so I write up what it earned and what it cost, and I put the numbers next to each claim.

What I run

Riffiter

Music ratings and discovery

Rate albums out of five, log what you actually listened to, and find records through people whose taste you already trust. Letterboxd, for music.
Tuval

Self-hostable workspace

Pages, databases and an infinite canvas over one set of records. Local-first, CRDT.
Gist

Trading signals, mobile

Follow buy, sell and hold calls on crypto and stocks in one place.
Friemind

Friendship app

Leave a post-it on a friend's wall, fill an intention jar, send letters to open later.

During the day I work on okul.com.tr and okulup.com, two education platforms used by schools and students in Turkey.

In the open

3 of my repositories are public, for different reasons.

claude-code-reviewer

MIT / Reads a pull request diff through Claude Code and posts inline comments on GitHub

This is the gap the rest of the site is about, closed one repository at a time. Agent-written code getting read before it merges, rather than after it fills a disk. It runs on a Claude Code subscription, so there is no API key and no per-review cost, and it is MIT because it should be easy to take.
Tuval

AGPL-3.0 / Pages, databases, issues and an infinite canvas over one set of records

Notes, tasks and diagrams are usually three products that do not share a row. This is one, self-hostable and local-first, because the alternative is renting the place your own thinking lives. AGPL so a hosted fork has to stay open.
claude-code-statusline-limits

MIT / Claude Code status line that projects when the 5-hour and weekly usage windows run out

Claude Code reports how much of a usage window is gone, which is not the number that decides whether to start a long task. This samples that percentage over a rolling 90 minutes, works out the rate the current session is burning at, and prints the clock time the cap would be reached if that pace holds. No warning means the pace is fine. One file, no dependencies, MIT, so installing it is a curl and four lines of settings.

What this site was

It was a directory of 143 browser tools. Formatters, converters, encoders, calculators. Everything ran client-side, which is still true and still the right call: nothing you paste is uploaded, because there is nowhere to upload it to.

Then agentic coding ate the category. Nobody opens a tab to format JSON when they can ask an assistant that is already looking at the file. 72 people visited in ninety days, which is the sound of a category closing.

So the tools became an archive. They still work and they are not going anywhere. The site is about the writing now, and the newest tool, an llms.txt validator, exists because a post needed it.

Elsewhere