Hello, I'm Jieun Jeong, a developer.

I believe a service only has meaning when people keep using it in practice.

While building Wiblog, an automated blogging SaaS, I kept asking what structure helps posts get indexed by Google, what titles people actually search for, and what operators publishing every day spend the most time worrying about.

Before adding more features, I believe the first thing to do is find where the person running the blog gets stuck and solve that problem.

Even when automating, I don't want to remove human judgment. I prefer leaving the materials people choose and the decisions they make in place, while handing repetitive collection, generation, and publishing to the system. If there isn't enough data to validate the result, I don't make easy claims about performance.

I treat the costs, delays, and possibilities of failure that arise in real operation as part of the design.

Ultimately, I don't want a service that only looks technically impressive. I want a service that is easy for users to use, manageable for operators, and able to recover when something goes wrong. This blog records what I chose, what I gave up, and why I later changed those decisions while building services like that.