The case for boring tools

Many of us software developers spend time on personal projects. Mine was/is a simple personal tech blog. When I first built it, I wanted to stick to the tools I was most used to: React.js Some SSR metaframework (Next or Gatsby) A JavaScript build system (Webpack back then) And that is what I did. I took a template for Ghost CMS and built a basic blog for fun. After writing for a couple of months and having updated my site over 50 times, I began to get small problems. 1. Writing became boring The way the CMS worked was by taking markdown content, adding some metadata to it like canonical links, metatags, etc., storing this info in a database (yes, this needed a server), and then triggering a build on the server-side rendered site. This meant that after the fun part of writing my little blog post, I had to go to an admin panel, log in, figure out all the metatags and attributes for my blog post, and fill out a massive form with a good amount of form validation (description cannot be long