About
About
2026-08-30sade.dev is a notebook of systems that actually run in production. I write about backend and systems engineering — PostgreSQL, Redis, Laravel, Nginx, queues and infrastructure — recording real decisions along with the constraints that forced them and the traps they hide. The aim is not another walkthrough but a reference an engineer can return to when the same decision lands on their desk. Beside the writing sits a small set of developer tools that run entirely in the browser.
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
This is the order I decide in.
- 01Nothing ships that didn't runEvery note comes out of a system I actually operated.
- 02Decisions come with their constraintsNot what I chose, but what forced the choice.
- 03Traps stay inThe wall I hit is as much of the note as the path that worked.
- 04Every recommendation has an expiryAdvice that won't say when it stops being right is unfinished.
- 05Boring tech gets defendedBoring is not cowardice, it's a budget decision.
- 06Publishing is slowCadence comes from accumulated experience, not from a calendar.
Scope
What I write
- NotesShort production notes on a single problem.
- SystemsArchitecture breakdowns, end to end.
- JournalDecision logs and what happened behind them.
- ToolsDeveloper tools that run entirely in the browser.
What I don't write
- Beginner tutorials"Your first Laravel app" is not here.
- Hype contentChasing a trend is not an engineering decision.
- Experience written by a modelEditing is one job, authoring is another.
- Product pitchesA pitch does not stand in for the writing.
Who writes this
Muhammet Şafak
I am a backend-focused software engineer. I have been writing code since 2008 and building systems that run in production for 15+ years. I work on scalable system design, performance optimization and engineering leadership, focused on shipping reliable, sustainable products by aligning technical decisions with business goals.
- GitHub
- @muhammetsafak
- muhammetsafak44
- Contact
- [email protected]
- Location
- Istanbul, Türkiye
How this gets written
The case and the decision are mine; AI is the editor here, not the author.
- 01DraftI pick the subject and write the draft around a production case I lived through.
- 02CleanupAI anonymizes the text and clears the typos and the broken sentences out of it.
- 03Final readI read it back line by line before it goes out, and fix whatever is left.