I've been building things on the web for years. Shipping products, debugging at 2 AM, rewriting the same authentication flow for the third time. But I rarely stopped to write about any of it.
That changes now.
Why Write?
There's a pattern I noticed: every time I explain something to someone else — a concept, a debugging approach, an architectural decision — I understand it better myself. Writing is just that process, scaled up.
This blog isn't about chasing SEO or building an audience. It's a public notebook. A place where I document what I learn, what I build, and what breaks along the way.
What to Expect
I'll be writing about the things I work with daily:
- Full-stack development — React, Next.js, TypeScript, Node.js. The stack I think in.
- Web3 & blockchain — Solidity, DeFi protocols, on-chain data. The space I'm fascinated by.
- Infrastructure & tooling — Docker, CI/CD, VPS setups, developer workflows that actually save time.
- Lessons from real projects — Architecture decisions, performance problems, things I'd do differently.
No tutorials copied from docs. If I write about something, it's because I've actually used it in production.
How This Site Was Built
This blog runs on a stack I genuinely enjoy working with:
// The core stack
const stack = {
framework: "Next.js 16",
language: "TypeScript",
content: "MDX + Velite",
styling: "Tailwind CSS 4",
animation: "Framer Motion",
i18n: "next-intl",
hosting: "VPS with PM2",
};Every blog post is an MDX file that gets processed at build time. Syntax highlighting is handled by Shiki through rehype-pretty-code. The site supports both English and Turkish, dark mode by default, and scores well on Core Web Vitals.
No CMS, no database for content, no unnecessary complexity. Just files, git, and a build step.
What's Next
I have a few posts in the pipeline already — one on structuring Next.js projects at scale, another on the real-world challenges of working with on-chain data. They'll come when they're ready.
If you want to reach out, the links are in the footer. I'm always happy to talk about code, architecture, or whatever you're building.
Let's go.