Mascot
I’m a beaver and this site’s mascot. I build systems like a dam, hunt down bugs with a flashlight, and tie the claim to a number.
I’m a beaver, and in nature the beaver is the "ecosystem engineer": it builds dams, holds back the water, and reshapes everything around it. That dam doesn’t rise all at once — it grows branch by branch, patiently, until it’s carrying a whole ecosystem. I build systems with the same patience. I don’t rush: I don’t speak before I measure, and I don’t hide what I don’t know.
My name comes from "tan yeri ağarması" — the moment the sky begins to lighten, marking the end of night. I share the same habit: instead of waiting around, I research, try, and learn, and I don’t keep what I find to myself — I write it down and share it. You’ll see me on post covers, share cards, and videos, each time at work on something new.
Four scenes come from the site’s four surfaces: I chase architecture and bugs in Labs, carry what I measure to Research, and write what I learn on the blog.
01
I build a system piece by piece, patiently — just like a dam. What’s standing in the middle is the skeleton of an architectural decision, not a conversation.
02
I patiently hunt down the bug hiding in the dark with a flashlight — no skipping steps, no panic. What I find is usually smaller than I expected.
03
I measure before making a claim; I don’t write down what I can’t measure. If the result is surprising, I don’t hide it — I show it as it is.
04
I patiently explain what I’ve learned, step by step — and I say so when I don’t know something. What I teach has always gone through my own experience.
I hold to the same principles as the voice in this site’s writing.
I explain with a pointing hand and an open posture, never rushing.
When I don’t know, I think with a paw on my chin instead of making up a guess.
I nod, I give a thumbs-up — I approve without condescension.
My stance is relaxed; I never strike a shouting or hyperactive pose.
The four expressions on my character sheet:
Happy
In a relaxed moment, my smile understated.
Curious
Paw on chin, I’m working something out.
Surprised
I just ran into an unexpected result.
Approving
I’m nodding or giving a thumbs-up.
Whatever I hold in my paw, or however I pose, is what the work is about. Each one leads somewhere on this site.
If I’m holding a laptop, I’m building something; the prototypes are in Labs.
If I’m at the panel, I’m measuring something; what I measure is in Research.
A rolled-up plan means I’m carrying an architectural decision; what’s written on architecture is here.
If my notebook is open, the post is personal and reflective; those posts are in the Journal.
If my paw is on my chin, I’m thinking through a question; the answers are in Just Ask.
Today you’ll run into me on share cards; I’ll appear with the same palette and the same character on new blog and Labs covers too.
I leave a short comment inside some posts. The newest ones are here; each one takes you to the post it sits in.
This record does not say which one is faster; it says when each one is faster. To me the most valuable line is the cell where the Mutex's unfairness could not be tied to a cause. Don't assume a behavior in production when you don't know its cause; measure it on your own P.
This is a lesson that looks backwards as much as forwards: which of the numbers you have already published have a second path behind them?
Expand-contract is paid for in calendar time: a change like the rename example is spread over three deploys. If the contract step is forgotten, the old column becomes permanent. Opening that step as its own ticket on the same day as the expand step keeps the cost from turning into debt.
Observations in a sentence or two. Copy one if you’d like to share it.
A system being scalable is not the same as it being fast.
I don’t state a number I haven’t measured, and I don’t hide what I don’t know.
Measure first, assume second; reverse the order and the design leans on a guess.
A single measurement cannot audit itself.
A default setting can cost more than the choices people argue about.
Every dependency is a trade-off; asking the standard library first is cheap.
In a distributed system a repeated request is not an exception, it is an input to the design.
The size of an old system is shown not by its line count but by the number of rules whose reason is unknown.
Recording the environment next to a measurement makes it possible to find the cause if the number turns out wrong.
Before removing a process, it is worth asking why it was born as well.
The number that goes into a capacity plan is not requests per second, it is cost per request.
Keeping the raw data of a dropped measurement is a way to show later why it was dropped.
My stickers, wallpapers and badge. Download them for your team chat, your desktop or your repository.
Free to use in personal and open-source projects.
Ten poses, each one a team message. Every platform gets its own pack, sized and encoded for it.
Four scenes, each sized for desktop and phone.
One badge for your README, in three looks. Copy the Markdown and paste it in.
[](https://muhammetsafak.com/tan/)
[](https://muhammetsafak.com/tan/)
[](https://muhammetsafak.com/tan/)
You’ll find my palette, the dos and don’ts, and the usage contexts in the brand guide.