Added categories tags to first blog post.

src/content/blog/_index.md

@@ -1,6 +1,6 @@
 ---
 title: "blog"
-description: "A collection of my thoughts, insights, and experiences."
+description: "All things open-source."
 date: 2023-03-27
 menu: "main"
 weight: 5

src/content/blog/dev_diary-finding-the-fun.md

@@ -1,6 +1,8 @@
 ---
 title: "dev.diary—Finding the Fun"
 date: 2023-01-23
+categories: [dev.diaries, open-source]
+tags: [open-source, homebrew, programming]
 draft: false
 featured_image: "/Images/techcrunch-gen-art.jpg"
 ---
@@ -39,8 +41,6 @@ After a few days I stopped laughing. I started getting excited. This hack wasn
 
 How do you use tea? You don’t. You use the tools that the open source ecosystem provides. If you read a blog post about a new tool then just type the commands you read into your Terminal and try it out. There’s no “figure out the package name and then install it step”. There’s no “will installing this break other stuff on my system” concerns. If you don’t like it then don’t worry about it—it’s already gone.
 
-
-
 tea still is a “universal interpreter” but that just falls under the general banner; we don’t have to explicitly name this feature; tea just knows how to make what you throw at it work. Be that a command or a script, tea makes it possible for you to get on with what matters: making your app.
 
 And so I dropped executable markdown completely. Part of the reason I added exe/md was the desire for tea to be a tool that makes development a dream. And we have achieved this because now if you want to use executable markdown to run the script build you just type xc build and tea installs xc transparently. Whatever “task runner” your project needs is transparently available. Having this feature in tea itself no longer made sense.