If you actually write a developer blog, it takes a lot of time. So I think it would be good to devise a strategy that suits meat7238's situation. If you are completely new to development -> Rather than writing a development blog, organize it in a personal notebook so that you can understand it well. If you have studied to some extent -> You can think more deeply about what you have learned, so organize it in a development blog so that others can understand it. If you can explain it to others, you will learn about the details that you missed. It will also be helpful in interviews, and you will be filled with confident content that you can include the blog address in your documents. I think it would be good to devise a strategy like this. Since there are many different formats for development blogs, I think it would be good to decide on a platform that you can use consistently and use it. Don't put too much effort into it, and if you relax a little and write one by one, you will have accumulated quite a lot before you know it. Fighting :)