ブログのページビュー300万が語る「実用主義の技術ブログの書き方」

While writing a technical blog, I often thought, 'What is a good article?' I wanted to write well, but my articles became messy and I spent more time writing them. As a result, I lost interest in my writing and ended up not finishing them. My greed created many worries. How should I organize the table of contents? What should my tone be? How long should the article be? How do I determine the difficulty level? How can I reduce the time it takes to write (write efficiently)? etc., I had a series of vague thoughts that were hard to define. In the midst of all this, I took this writing class and all my worries were solved. I even had the opportunity to learn a lot of additional tips (images, AI, SEO, etc.). → If you are curious about how I solved my problems, I highly recommend taking the class! It is amazing that I can learn the insights I have gained from running Gltto for 10 seasons at such a low price. If you are thinking of starting a blog, I recommend taking this class before you start. You will be able to write efficiently without wasting time on worries. I highly recommend this class!

I have been running a blog consistently, but at some point I fell into a rut and took a class. After completing the class, I realized that I had been focusing only on the act of writing. I had to think again about the purpose of running a blog, and I was able to consider a more systematic writing pipeline beyond just writing. I recommend this class to those who are just starting out with a tech blog, but I think it is a good class that provides different perspectives and experiences to those who, like me, have focused only on the act of writing. (I wrote in more detail about the content of the class and what I felt. https://junior-datalist.tistory.com/400)

I really enjoyed Kyle's lecture! It was a great time to think about many tips and the direction of my future blog operation during the not-so-short time of 4 hours and 30 minutes. I'm going to try to run my blog with the goal of completion, not perfection, from now on, because I'm afraid that if I don't take action right away, all these great lectures will just pass me by!

Hello~ Thank you for taking the time to give us a great lecture. First of all, there were a lot of stories that I could relate to while watching the lecture. The concerns that arise when readers of a technology blog become others and the fact that writing without sufficient understanding can be counterproductive. As I watched, I couldn't help but think, "Are you talking to me?" Next, the parts on worrying about topics and setting goals for the article, and adjusting the difficulty level of the article, came to me as clear solutions. On the other hand, it may not be suitable for those who want a direct methodology for writing development articles. In my opinion, the intention of the lecture is not simply to convey technology, but to provide guidelines to form writing habits and help you find your own style. In conclusion, I dare say that it will be a good milestone for those who have just started writing technology articles or are just starting out like me. I recommend it!

Thank you for creating the lecture! :) Thanks to you, I was able to solve the problems I had. I realized the importance of writing and have been writing for about 5 years, but until recently, I repeatedly experienced the following problems: 1. Lack of writing material. (I don't know what to write about.) 2. Unsystematic writing comes out. (I don't know how to structure the writing.) 3. Low number of views. (I'm upset that no one is reading the articles I worked hard on.) 4. Lack of confidence. (I feel like I'm not good at writing, and I wonder if I should keep writing.) 5. I don't want to write anymore. As I experienced these problems, I lost direction or stopped because I had writer's block. I recently experienced a similar situation. Then I came across Kyle School's lecture and was able to solve a large part of the problem. So, I think it will be very helpful for those who are having problems with writing like me! Thanks to the lecture, I realized a lot of things, and I would like to summarize the three biggest things I felt as follows: 1) The problem I had is not 'my own problem'. The lecture presents various problems and solutions that arise when writing, including the problems I experienced above. I felt that they had faced and overcome these problems directly for a long time, accumulated know-how, and put all of that content into the lecture. Thanks to this, I realized that most of the problems that writers face are similar, so when I face a problem, I recognize that it is 'a problem that someone has solved' and focus on the solution. 2) It is important to create your own writing standards. The good thing about the lecture is that it covers practical content that can be used immediately, but it also provides guidance so that you can solve problems yourself. Each person has different environments and contexts, so some methods may not be suitable. In such cases, I think it is very helpful to know what you thought and what processes you went through to solve the problem, rather than the method. The lecture kindly deals with these points and helps you create your own standards. This was the best part of listening to the lecture. It covers various practical methods such as writing pipeline, structuring, and SEO, but it also tells you the importance of setting your own standards and helps you create those standards, which was especially useful. 3) The key is to 'keep writing'. I think everyone has different purposes for writing, such as studying, monetizing, and preparing for a job change. I mainly wrote for studying, but I really wanted more people to read my articles. But in the end, I realized that the key is to keep writing. The lecture presents various methods such as how to solve problems that arise when writing, how to write a little easier, how to improve quality, how to get many people to read it, and what to be careful of. But after listening to these methods, I realized that the essence is writing itself, and the key method to achieve the purpose is to create my own standards and keep writing. And that each method helps me to keep writing. The content has become long, but after listening to the lecture, I solved the problems I had when writing, created my own standards, and started writing steadily. If you are having similar concerns to me, I recommend listening to the lecture :)