Have you ever built something just because you wanted to learn how to build it? And once your curiosity was satisfied, you just canned your creation?
I've been there many times with my attempts at blogging. My last public post dates back to 2007 when I had set up a small travel journal for a trip to Thailand. Since then I've built several blogs. For example, I developed one in 2018 while I was learning
Nuxt. Yet when the blog was ready to roll, I canned my work without ever writing content. But... why?
Actually, time and curiosity...
I believe that, apart from time, one thing plays a major role there for me: Curiosity. The very moment that one curiosity is satisfied (learning a new framework), it is replaced by a new one (I need to learn
<xyz> too!). Developers are doomed for their curiosity. There's a never-ending list of things emerging. New ways to build stuff. New architectural models. New languages. New frameworks. Cleaner, leaner, faster, better. And, oh my, does it take time.
...killed a blog.
By now you'll know where this is going. Curiosity is a blog murderer because you'll have to weigh up polishing your notes for a public audience versus learning the next great skill to have. This is why more than once for me, curiosity killed a blog.
A Noble Death
But here's the good news: It doesn't matter.
Curiosity is the very basis of education and if you tell me that curiosity killed the cat, I say only the cat died nobly. ― Arnold Edinborough
It doesn't matter when yet another app of yours got squeezed into the virtual tin of an archived git repository. It doesn't matter when you build a blog but never write content. Because by satisfying your curiosity you'll learn something new, and you'll gain something from it. Be it knowledge, experience, employability, fun, or simply, satisfaction.
Albert Einstein put it this way:
The important thing is not to stop questioning. Curiosity has its own reason for existing.
Now, this blog has obviously survived, and the reason is mostly that the COVID distancing rules have allowed me to use some of the extra time to reconsider. As a result, you'll find my developer notes on this blog. Sometimes more brief, sometimes in more detail. But I hope they'll be useful to some.
If you're curious about the stack this blog was built on, here's a quick list:
- Svelte - the UI framework/compiler
- Sapper - a Svelte app framework (features incl. code splitting, routing, etc).
- Tailwind CSS - a CSS utility class framework
- Material Design - the design principles this app is built on
- AWS S3 - Hosting the static SPA
- AWS CloudFront - global distribution/cache
- AWS Lambda@Edge - request path helper
- Gitlab Pipelines - to build and deploy
And that's it for my intro to this blog. See you soon!
Enjoy every step you take. If you're curious, there is always something new to be discovered in the backdrop of your daily life. ― Roy T. Bennett, The Light in the Heart
* No cats were harmed for the creation of this post. Similarities to real creatures are coincidental.