Hello, and welcome to Refactored Telegram, a blog about my adventures in software development.
I have been meaning to start a blog dedicated to working in software for a while. As a professional developer and someone who builds side projects in his spare time, I occasionally write on the topic in my personal blog. But it felt a little strange interleaving my thoughts on the subject alongside my day to day blog entries. I felt it was necessary to put together a separate blog for posts that relates to my professional and personal work, which is the reason for the existence of this blog.
As to what this blog will cover, all I can say at this time is that it will be pretty much geared towards my learnings and experiences which are somewhat relate to software or software development. I’m sure there will be a fair few posts on Go, as that is the language that I’m currently using, but it will be unlikely that that is all I’ll be talking about. The tech landscape is constantly changing, along with my preferences, and there may come a time when I no longer want to work in or talk about Go (although that time will not come soon). My previous, aborted attempt to write a development blog exclusively on Go would have locked me into that topic and, although I enjoy working with the language, I’m not nearly proficient or invested in it to make that all that I cover on this blog.
In addition to Go and other “objective” topics in software development, I’ll probably also talk about my personal projects or opinions on software development practices as a whole. I want to keep the topics on this blog rather open ended at this stage. Maybe as time goes by, I might find a niche that I can focus on. But for now, I’ll probably just stagger around, writing about anything tangentially related to software development that strikes my fancy.
Finally, about the name. To be honest, I’m terrible at naming things (I also need to avoid purchasing domain names for each terrible name that I come up with). The name Refactored Telegram was a randomly generated suggestion from GitHub, and it seems to work perfectly. So much of classic computation was built from the telegram infrastructure like the use of teletype machines as terminals to the ASCII encoding system. It seems fitting to recognise that the technology of today is built upon the technologies of yesteryear.
Anyway, we’ll see how this blog will go.