･
Reviews 3
･
Average rating 3.7
I personally was not satisfied. A technology blog can be used in many ways, but for me and those around me, it is usually used as a portfolio for job changes, and from that perspective, it was not very helpful. If you leave out the word "technology" and just say "growing a blog," it might be different, but I wonder why the keyword "technology" blog was added. The content for growing a "technology" blog is very small. From that perspective, I wonder if this course content is worth paying for... I bought it at a 30% discount as an early bird, but I think it would have been fine if it had been uploaded as a free 2-3 hour lecture on YouTube, which covers similar content to growing a blog, but I don't think I would recommend it to anyone around me, so I'm writing this honestly.
Thank you for your honest feedback, clang🙏 This lecture starts with the question of how to write fundamentally and includes my experiences running a tech blog. I shared real-life examples of what types of posts are effective on a tech blog and the characteristics of good posts, and I also covered the process of writing specific tech posts like DuckDB. There is also content on how to write consistently. I have seen people who have included a tech blog in their portfolio and consistently written good posts receive good reviews and get promoted. Since consistency is the hardest part, I focused on practical methods to achieve it. I am sorry that I did not satisfy you, clang. What content would be helpful to you? Let me know and I will add it. I can also show you good posts that can be used in your portfolio. There are many possibilities, so please let me know. I want to help you as much as I can. Thank you for reading
Hello clang! It's been a while since I left a reply. I've been continuously thinking about how to reflect the feedback you provided. What do people who write blogs as portfolios need? These kinds of considerations. As a result of my contemplation, I've categorized different articles into levels based on my experience reading various posts. Of course, this part has subjective elements, but I still think it could be helpful for those utilizing portfolios. I've defined them as Lv1 ~ Lv4, and to put it simply: Lv1: Simple book summaries, TIL, coding algorithm solutions Lv2: Technical usage articles (e.g., How to use Docker Composer, etc.) Lv3: Experience-based problem-solving articles (regardless of whether it's Project or Task) Lv4: Insight-providing articles (e.g., Things I've learned from 10 years of development, etc.) If you're writing a blog as a portfolio, having Lv3 content would leave a good impression. I've added it to the final section of the course, so please take a look when you have time. https://www.inflearn.com/courses/lecture?courseId=334432&tab=curriculum&type=LECTURE&unitId=333242 I hope the content I've shared will be of some help to you 🙏
