---
title: "About"
description: "About Muhammet Şafak and sade.dev — why it exists, where it is going, what gets written here and what does not."
url: https://sade.dev/en/about/
lang: en
author: "Muhammet Şafak"
updated: 2026-08-30
---

# About

> About Muhammet Şafak and sade.dev — why it exists, where it is going, what gets written here and what does not.

## Vision

What Turkish technical writing is missing is not another introduction; it is a reference
an engineer can return to when the same decision lands on their desk. That is where
sade.dev is going: an archive of decisions that still show which constraint produced
them, years after they were made.

I measure that three ways. A piece cited as a source in Turkish engineering
conversations. An engineer who arrived for a tool staying for the writing. A site that
opens like documentation rather than like a marketing page.

The notebook will get larger. It will not get faster.


## Principles

- **Nothing ships that didn't run** — Every note comes out of a system I actually operated.
- **Decisions come with their constraints** — Not what I chose, but what forced the choice.
- **Traps stay in** — The wall I hit is as much of the note as the path that worked.
- **Every recommendation has an expiry** — Advice that won't say when it stops being right is unfinished.
- **Boring tech gets defended** — Boring is not cowardice, it's a budget decision.
- **Publishing is slow** — Cadence comes from accumulated experience, not from a calendar.

## Scope — What I write

- **Notes** — Short production notes on a single problem.
- **Systems** — Architecture breakdowns, end to end.
- **Journal** — Decision logs and what happened behind them.
- **Tools** — Developer tools that run entirely in the browser.

## Scope — What I don't write

- **Beginner tutorials** — "Your first Laravel app" is not here.
- **Hype content** — Chasing a trend is not an engineering decision.
- **Experience written by a model** — Editing is one job, authoring is another.
- **Product pitches** — A pitch does not stand in for the writing.

## How this gets written

- **Draft** — I pick the subject and write the draft around a production case I lived through.
- **Cleanup** — AI anonymizes the text and clears the typos and the broken sentences out of it.
- **Final read** — I read it back line by line before it goes out, and fix whatever is left.