Studio Opens

The first post. A quick note on why I started this site.

Why a Site

I've been heads-down building things on my own, and once a project is done, it just goes into a code repo. Over time I noticed a few problems with that:

• No record of the process — once it's done, I've already forgotten it
• No way for non-developer friends to see what I've made
• No feedback channel — I never know how others perceive it

So I started this site. It's not about marketing. It's a versioned workbench for myself.

What I'll Write

I'm planning three kinds of posts:

1. Dev logs — the trade-offs and gotchas while building a feature
2. Tool notes — things I've used and think are worth recommending
3. Essays — day-to-day thoughts from an indie dev

No promises on update frequency. I'll write when I have something to say.

Why This Format

I've tried a few publishing approaches and ended up with a lightweight, easy-to-maintain site. The reasons:

• Articles and code are versioned together
• Low maintenance cost
• Fast loading, good reading experience
• A place where readers can leave feedback

Suits someone like me who wants to maintain things slowly on their own.

If you've read this far, feel free to leave a comment below.