Why I Started Blogging Weekly: Learning in Public on AI, Code, and Teams

Why I started a weekly blog as learning in public: what I'll write about AI, coding, and leading teams, plus an invitation to say hello in the guestbook.

Kasidit Wansudon4 min read
writinglearning-in-publiccareerai

Hello, I'm Kasidit Wansudon, a Thai full-stack developer. This is the first post on this blog, and I intend to write every week. In this post I want to explain why I'm starting a weekly blog as learning in public, what I'll write about, and invite you to say hello in the guestbook.

Who I Am, Briefly

Before writing code, I worked in logistics and construction. Then I studied Software Engineering at Sisaket Rajabhat University and started taking freelance work while still studying. Later I worked as a Mobile Developer building a Flutter POS, and today I'm a full-stack developer building internal tools for operations in 12 countries with Laravel, Vue, MySQL, and the cloud.

This path hasn't been very straight, and I think that's one reason I want to write.

Why Write

1. Write to Think Clearly

I've found that I truly understand something only when I can explain it to someone else. Many times I thought I knew a topic well, but when I tried to write it out I got stuck by the second paragraph. Writing forces me to fill gaps I didn't know existed.

2. Learning in Public

Learning in public means sharing what you're learning along the way, instead of waiting until you're an expert. The benefits are:

  • People at the same stage as me benefit, because I still remember what it was like not to know
  • People who know more can point out where I've misunderstood
  • I get a record to come back and read in the future

I'll try to write honestly, covering both what worked and what broke, because lessons from mistakes are often worth more.

3. Answer the Same Question Once

At work I'm often asked similar questions again and again, such as how to set up an index, how to deploy so that you can roll back, and how to use AI to write code without breaking things. Writing a post lets me answer in detail once and then send the link to the next person.

Topics I'll Write About

I've split the main topics into three groups.

AI in Software Development

I use AI to help write code every day, and I've seen both where it helps a lot and where it wastes time, such as the AI inventing variables that don't exist or going back and forth on a bug without ever finishing. I'll write about how to work with AI effectively, the rules I use, and what not to trust.

Coding and Backend Systems

Things I really do every day, such as MySQL query optimization, Laravel, deployment, Git workflow, and designing systems used across many countries, plus looking back at old work such as a Flutter POS that synced over MQTT.

Teamwork and Leading Teams

The longer I work, the more I see that most problems aren't in the code but in communication, handing off work, and making decisions together. I've only just started learning this, and I want to write as I learn.

The Format of Each Post

I've set a few rules for myself.

  • Write from real work. I won't write about things I haven't done.
  • Include something usable. Every post should have steps, a checklist, code, or a way of thinking that you can take and use.
  • No longer than necessary. You should be able to finish it in one coffee break.
  • Don't reveal internal workplace information. I can share lessons but not confidential details.

An example of the outline I use to draft every post:

1. The problem I ran into (why this matters)
2. What I tried that didn't work
3. What worked, with steps or code
4. Cautions
5. Summary

Why Weekly

A weekly cadence forces me not to wait for everything to be perfect. If I wrote once a month, I'd polish for so long that I never published. If I wrote every day, I'd have no time to do the real work I would write about. One post a week is the balance I think I can sustain for the long run.

Of course, there will be weeks when work is so heavy I almost don't get to write. So I always keep a list of backup topics.

Say Hello in the Guestbook

This blog doesn't have comments yet, but it has a guestbook where you can leave a message. If you'd like me to write about something, have questions about my work, or just want to say hello, leave a note. I read every message, and topics people ask about will get priority.

Summary

I'm starting a weekly blog because I want to think more clearly, learn in public, and answer the same questions in detail just once. The main topics are AI in software development, coding and backend systems, and teamwork. Thank you for reading this far, and see you in the next post.

Questions or thoughts?

Leave a note in the guestbook or reach me on X.