./greetings
$ git add .
$ git commit --message "Initial commit; Hello world!"
$ git push --force origin/mainIf you — who is not me — stumbled upon this site or this particular post, welcome! And… I’m sorry.
Why am I apologizing?
Well, as you can see, or… lack thereof, nothing is interesting here… so I’m sorry that you spent some time, bandwidth, or even precious data just to visit this instead of something more interesting.
Anyway, welcome to my very first blog post — a first commit, if you will — in which I will talk about why. Why did I create this website? Why bother making it in the first place? Why would I spend some restless weekends just for this?
My reasons:
- A “cloud backup” of my knowledge base
- To have a piece of ownership in this world of the internet
- To showcase… something
- A digital presence, like everyone else
- Finally, I am putting my domain name that I bought years ago to good use
BUT! Before I continue to the content of the topic, you might be wondering what’s with the ~ and ./ patterns in my navbar and/or in this blog post, or maybe not… anyway, the reason is, I like how Unix/Posix file paths look like, so I’m using it as a sort of a bearing of direction in my blog, as well as to differentiate between regular text content and some “landmark” so to speak.
That’s it, now let’s back to the topic.
./knowledge-base-backup
I often find something interesting and do something interesting (at least interesting to myself), and sometimes I have to deal with something less interesting as well such as fixing my GNU/Linux installation (I use Arch btw), which is fine and all, but the problem is, once I do it or solve something, I usually don’t get faced with the same interesting situation or problem for a quite lengthy time, to which when I ultimately faced with one, I have to remember how I deal with it, or if I’m lucky, I probably have the steps or files still around in my storage, but if I’m not lucky, I have to remember what I need and search through the interwebs, which either still exists, I can’t find it, or the web has been nuked from the face of the internet forever.
So I hope that in addition to my local copies of step-by-steps, tutorials, config files, etc. I also have a backup that reside in the internet for quicker access since I don’t have to rummaging through the whole disk to find it.
./piece-of-internet-ownership
The Internet is supposed to be for everyone, and anyone can have a piece of it — at least, that’s what I think. Of course, yes, I know it’s not that simple… and to be fair, nothing ever is.
Still, at least by making this personal website, I get to “own” a part of the internet — this blog, with my domain as the address. And I can do anything I want with it (within reason, law, and regulations… I guess).
./showcase
With my work in backend and game development, I may or may not have planned to showcase something to the internet, or at least share it with people I know. Having my own personal website will at least help as my target “platform”.
./digital-presence
Among my developer acquaintances, some of them have their own blogs, which makes me feel left behind. So with this, I’m finally catching up… I guess. At least now, I can “brag” that I have my very own website!
./utilising-domain-name
You see, I’ve had this domain for quite some time, but for the longest time, I just used it with Cloudflare to redirect to my GitHub profile. Basically, it was just a crappy URL shortener… but not anymore!
./closing
That’s all I can say for this post. The next one is probably going to be about how I wasted my weekend modifying this particular Astro template to suit my needs (well, not yet, but I’m working on it), so until then, take care and have an amazing day!