About

About Writing on This Blog

This is a space to record my experiences and experiments as a developer.

Why I Record My Experiences

Tutorials are helpful, but I’ve always found more value in posts that share other developers’ trial and error. They show not just the right answers, but which paths to avoid and why certain decisions were made.

Now I’m able to write those kinds of posts myself. There are already plenty of explanations for concepts like JavaScript’s execution context. Instead, I want to document the processes I go through while developing.

What I Write About

This blog documents projects I’ve personally worked on and my experiences with them. I write about technology choices made during side projects, lessons learned from maintaining open source, and technical patterns applied in real work.

Although this is a tech blog, I don’t write only about technology. I also try to record why I chose certain technologies, what decisions I made in different situations, and the thoughts I had at those moments.

I don’t only write about successes. I also document failed attempts, wrong choices, and what I learned from those experiences.

How I Write

I follow chronological order. I write about encountering problems, trying solutions, failing, and trying again.

I write in series. When documenting real experiences and the thought processes behind them, posts naturally get longer, so I prefer splitting them into multiple articles.

What This Blog Aims For

This is both a tech blog and a development diary. Rather than perfect solutions, I aim to document the process of trying.