Should we still write software engineering blog posts?
We initiated this blog with the realization that we were consuming a lot of content on the internet without actively contributing. As software engineers, both as a hobby and professionally, we have become accustomed to relying on search engines to find solutions and complete our software projects. Often, our queries led us to blog posts, Stack Overflow threads, or forum discussions where we discovered the answers we sought.
Hence, we naturally created this blog as a way to document our own software engineering discoveries, hoping to assist fellow engineers who may encounter similar challenges. Initially, it worked well, serving as a valuable resource for others. However, as we enter the era of artificial intelligence, the way people seek software engineering solutions is changing. Traditional search engines are being replaced by AI language models like Google Bard and ChatGPT, which provide direct answers. There is no longer a need to sift through blogs, forums, or personal websites to find solutions.
Given this new reality, one might question the purpose of continuing to write these concise blog posts that aim to address specific engineering issues. Initially, it may seem unnecessary. After all, why maintain personal notes when the answers are just a chat away?
