Building zafir.dev

I’ve always liked the idea of having a small, focused corner of the internet just for developer things. Not a portfolio, not a landing page, and not a place where I feel like I have to present anything perfectly. Just a space to write, experiment, and collect the small ideas that usually disappear into screenshots or random notes.

zafir.dev is exactly that.

So why not just use adamzafir.com?

My main site already does what it needs to do. It’s a portfolio (kinda). It shows the projects I’ve shipped and the things I care about. But it isn’t a great place for:

• half-formed ideas
• SwiftUI patterns I want to reuse
• build notes
• random debugging discoveries
• experiments that don’t deserve a full repo
• things I want to write down before I forget

A dev site doesn’t need the same level of polish or structure. It just needs clarity and a good place to think out loud.

Why a custom site and not Notion, Medium, or anything else?

I wanted something that feels like a tool instead of a platform. I also like the feeling of owning the entire stack.

What this site is for

zafir.dev is where I’ll put:

• dev notes
• writeups on small UI patterns
• Swift and SwiftUI experiments
• thoughts while learning new tools
• things that are too technical or niche for a portfolio

It doesn’t need to be perfect. It just needs to be useful, mainly for me, and hopefully sometimes for someone else who builds similar things.

Closing thoughts

This site is more of a dev notebook than a blog. A place to write things down before I forget, collect patterns I keep reusing, and store the little discoveries that happen while building bigger things.

If it ends up helping anyone else, that’s a bonus.
Even if it’s only useful to me, it’s still worth having.