Thoughts on Starting a GitHub Blog
Developers are pioneers and problem solvers.
They should not be afraid of challenges and should be open to solutions that go beyond code.
1. Why I Start a GitHub Blog?
The world is vast, and there are many developers. If you want to be a unique presence among the many developers, you need to work harder and challenge yourself in various fields. There are so many areas to study, and new fields and skills are constantly emerging. Even if I learn something, I often forget it after a few months. Sometimes, I can’t find the materials I studied before, even when I search online.
I needed a place where I could look back at what I learned. That’s why I started a GitHub blog. I wanted to learn about creating a Git blog using GitHub Pages and Jekyll, which was a field I wasn’t familiar with. I actively tried to learn about making GitHub blog, which was a new field for me.
Additionally, I thought I needed a technical blog to show my value. A GitHub blog is perfect for showing what I know and the projects I’ve worked on. It’s also great for connecting my GitHub, LinkedIn, and projects. This helps me show my resume better. It makes it easier for people to see my work and skills.
2. Difficulties in Creating a GitHub Blog
I didn’t start by following the Jekyll tutorial; instead, I used open-source blog codes and themes available on GitHub to create one directly. Using the existing GitHub blog themes, you can create a sufficiently attractive blog, and if you have frontend knowledge, you can customize the blog to fit your liking. However, the challenging part was dealing with unexpected errors when running the blog’s local server or deploying it with GitHub Actions. Another challenge was modifying CSS, which is always tricky T_T
If you don’t have experience solving such errors as a developer, I think the entry barrier is higher compared to other blog creation tools. I also resolved the Git blog errors by referring to other people’s blogs.
See my GitHub Workflows YAML file for reference.
3. Blog Content
I believe that for this blog to be vital and valuable, it needs to be updated consistently. Ideally, I would post once a week, but I don’t want to force out content or write low-quality posts. Nonetheless, I plan to post at least once every two weeks. I intend to organize my wide-ranging interests, from development and design book contents to web development, game development, and algorithms (coding tests), on this blog.
Additionally, if you truly want to differentiate yourself from others, writing content in English could be beneficial. If not only Korean developers but also people from around the world read my blog, it would further increase my value. Well, I have very poor English conversation and writing skills, so one purpose of posting in English is to improve my English skills. My English isn’t very good, so writing in English will help me improve my skills. I’m sorry if you find any grammar mistakes.
4. Continuity
I don’t know how long it will take for my posts to be read by a lot of people and become popular. I’m going to manage my blog for at least 10 years, and I’m going to keep trying to accumulate knowledge in the future. If the direction of my blog becomes clearer over time, I’d like to focus on writing more specific articles.