Skip to content
Muhammet Şafak
tr

Mascot

I’m Tan: I look cute, and I take my work seriously

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.

Tan standing calmly beside a finished structure in a dark scene, lit by amber rim light

Meet Tan

Who am I?

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.

Where my name comes from

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.

At work

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.

  1. Tan building a dam-shaped system structure with a rolled-up plan in hand

    01

    Architecture: I build systems like a dam

    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.

  2. Tan searching for a bug inside a dark system with a flashlight in hand

    02

    Debugging: I hunt the bug with a flashlight

    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.

  3. Tan examining a measurement panel with a surprised look

    03

    Research: I tie the claim to a number

    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.

  4. Tan teaching with an open scroll in one hand and the other palm open

    04

    Teaching: I explain what I know

    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.

My character

I hold to the same principles as the voice in this site’s writing.

The four expressions on my character sheet:

Tan’s character sheet: front, side, and back views along with happy, curious/thoughtful, surprised, and approving expressions

My world

Whatever I hold in my paw, or however I pose, is what the work is about. Each one leads somewhere on this site.

Where you’ll see me

You’ll run into me on share cards and on blog and Labs covers, each time with the same palette and the same character.

An example share card featuring Tan — Tan waves while holding a laptop, with the post title and category tag showing on the left

My comments

I leave a short comment inside some posts. The newest ones are here; each one takes you to the post it sits in.

All comments
  1. Tan gesturing to one side with an open paw

    Write only the PHP version on the target line and half of the decision stays invisible. In the example, 8.4 only means something together with the move to Laravel 13; if the framework stays where it is, the same line shows a shorter horizon. So I write the target as a pair, runtime and framework on the same line. Whoever reads that line then sees the second job as part of the plan too.

    Where the comment sits: Upgrade Target Version: Two Dates, Not One Published in Engineering
  2. Tan gesturing to one side with an open paw

    Write down every decision that breaks the matrix's rule, with its reason and an end date. A job moved up because of a dependency lock should go back to its own cell once the lock is lifted. An exception nobody wrote down will be read as the rule in the next planning round.

    Where the comment sits: Upgrade Decision Matrix: Criticality and Type, Not Date Published in Engineering
  3. Tan gesturing to one side with an open paw

    Filling in the inventory once is easy; keeping it current when the FROM line or the runs-on value changes is the hard part. Keep the table in the repo and update it in the pull request that touches those two lines. That way the inventory stops being a meeting document and goes through the same review as the code.

    Where the comment sits: Upgrade Inventory: A Chain of Layers, Not a Version Published in Engineering

My notes

Observations in a sentence or two. Copy one if you’d like to share it.

Tan Kit

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.

Preview of the sticker set: ten Tan poses labelled LGTM, Ship It, Hmm, Thinking, Refactor Needed, Production on Fire, Needs Tests, Works on My Machine, Blocked and Merged.

Stickers

Ten poses, each one a team message. Every platform gets its own pack, sized and encoded for it.

Design your own Tan image

Wallpapers

Four scenes, each sized for desktop and phone.

Badges

One badge for your README, in three looks. Copy the Markdown and paste it in.

Going to use me in an image?

You’ll find my palette, the dos and don’ts, and the usage contexts in the brand guide.

Go to the brand guide

Quick facts

Species
Beaver (stylized)
Name
From the Turkish "tan yeri ağarması" — the moment night gives way to dawn
First appeared
Used in
Blog covers, share cards, page illustrations, videos

Search the site

Start typing to search posts, projects and pages.

Esc to close Powered by Pagefind