DEV Community

ryo ariyama
ryo ariyama

Posted on

Reflections on My First 10 Blog Posts: Lessons, Challenges, and Next Steps

Introduction

I’ve now published 10 blog posts, so I’d like to take a moment to reflect on the experience so far.

What Went Well

As I wrote in this post, I originally started blogging because I didn’t have many opportunities to share my thoughts or output my ideas.

My purpose hasn’t really changed since then, but by writing these posts, I’ve been able to review and reinforce what I learn day to day — and that’s been really helpful.
Personally, I tend to forget the details of what I’ve implemented after about a month, but I feel like I remember the contents of my blog posts quite well.
Also, writing a blog often requires doing additional research, so I feel like I’ve deepened my knowledge in the process.

On top of that, this experience has helped me understand what kind of engineer I am.
I usually work across different technical areas and don’t have a clear title like “Backend Engineer.” or “Infrastructure Engineer.” So I hadn’t really known how to define myself. But looking back at the posts I’ve written, many of them are about infrastructure-related topics — so I guess I’m more of an infrastructure engineer who can also do backend development.
I think this could be useful when I look for new opportunities in the future — though, unfortunately, I haven’t actually had any interviews during this time.

Challenges

While there have been a lot of positives, there have definitely been challenges too.
First of all, to be honest, publishing a blog post every week is pretty tough.
I’ve often found myself thinking that I could have spent my precious days off doing something else — for example, working on a side project or planning a personal trip instead.

Also, although I didn’t mention this in my introduction post, I have a personal rule: I must write each post within two hours.
The reasons are simple — I don’t want to spend too much of my weekends on blogging, and I feel that spending more time would just result in longer, possibly harder-to-read posts.
Keeping this rule has actually been pretty hard for me. But on the bright side, it forced me to find ways to write more efficiently, which I think was a good thing.

For example, I used to create diagrams myself in draw.io, but I switched to using AI to generate ASCII art instead.
I also experimented with generating drafts based on my headings and outlines using AI, then adding my own explanations.
Of course, most of the sample code is also generated by AI and I even ask AI to review my drafts.
I still come up with the article titles myself — though sometimes I get suggestions from AI too.
Obviously, it wouldn’t make sense to have AI write a reflection post like this one, so I wrote this one entirely by myself.

Sometimes I wonder if relying on AI like this is a bit of a shortcut, but if I can achieve my goal in a short amount of time, I think it’s good enough.

What’s Next

I still believe that outputting my thoughts is important, so I plan to keep blogging until I run out of ideas.
Maintaining motivation to post regularly is really tough, so I hope to keep exploring better ways to stay motivated — maybe I’ll write about that too.

Ideally, I hope this blog will help me find new work opportunities or expand my network.

Lastly, I’d like to say thank you to the people who shared my posts and reacted positively on SNS like X and LinkedIn.
Thanks to them, some of my articles reached a wider audience than I ever expected.
I really appreciate it.

That’s all for now.

Top comments (0)