First Post

This is the first post on this site, which I built with Astro after experimenting with a handful of other frameworks and static-site tools. A few months ago, Astro wasn’t even on my radar.

I’ve wanted my own place to write for years—not another account on a publishing platform, but a website I could control, change, break, rebuild, and keep around for as long as I wanted.

That’s what I’ve always liked about personal websites. You can shape them around your own ideas, make them feel like your own, and continue improving them over time. You’re not entirely independent of hosting providers or other services, of course, but you retain control over the content, the presentation, and the direction of the site.

I first registered this domain in 2009. Content management systems, especially WordPress, were becoming the standard way to build and manage websites. I understood the appeal and appreciated how much they made possible, but I never became particularly interested in developing WordPress themes or plugins.

I was more interested in the web itself: HTML, CSS, JavaScript, browsers, servers, and the way all of those pieces fit together. Learning the architecture and conventions of a specific CMS never appealed to me as much as working with the broader technologies behind the web.

Where It All Started

My interest in web development goes back to my teenage years, around 2004. That was when I started building simple static pages and uploading them to free hosting services.

At first, I was learning basic HTML and figuring out tools like Microsoft FrontPage. But the part that really captured my attention wasn’t the software or the markup itself.

It was the idea that I could create something on my own computer, publish it, and make it available to anyone with an internet connection. Other people could visit it, interact with it, and actually use something I had made. That felt remarkable to me at the time, and it still does.

My interest in web development continued to grow, although I didn’t follow a straight path. Other responsibilities, changes in direction, and periods away from development kept me from pursuing it consistently.

But I kept coming back to it.

The tools changed. The web changed. My interests changed too. The desire to learn how things work and build things of my own never completely went away.

Why I’m Writing Again

I’ve been reading blogs in both Persian and English since I was a teenager, and I’ve occasionally written online myself.

A large part of what I know came from people who took the time to document their work and publish it: developers explaining how they solved a problem, engineers writing about decisions and tradeoffs, and people openly sharing what they had learned through experience.

Those posts were often more useful to me than formal documentation or polished tutorials. They showed not only what worked, but how someone thought through a problem, what went wrong, and what they would do differently next time.

Social media has changed the way people publish and discover information, but I still think personal blogs serve a different purpose. They give us room to slow down, develop an idea, document what we’re learning, and write without shaping everything around a platform’s format, algorithm, or character limit.

A blog can also become a long-term record of how someone’s thinking and work have evolved. That’s something I’d like to build here.

What I’ll Write About

Mostly, I plan to use this blog to document what I’m learning and what I’m working on.

I’ll write about software development, software engineering, artificial intelligence, and technology in general. Some posts may cover websites, web applications, tools, experiments, or other projects I’m building. Others may focus on a technical problem, a concept I’m trying to understand, or lessons learned from something that didn’t go as planned.

Not every post will be a tutorial, and I don’t expect every subject to be entirely new. Sometimes the most useful thing I can do is explain an existing idea in my own words, record the decisions behind a project, or write down what I wish I had known when I started.

I’ll occasionally write about hardware as well, especially when it overlaps with software or something I’m actively exploring.

Outside of technology, I’m interested in literature, music, and the arts, so those subjects will probably appear here from time to time too. I don’t want this site to be limited to a single category. It should reflect what I’m genuinely interested in, even when those interests don’t fit neatly together.

If something I write helps another person understand an idea, solve a problem, or start building something of their own, that’s enough reason to keep writing.