I recently changed this site generation from using Hexo (a JavaScript static site generator), to Hugo (a Golang-based one) and it made me happy for quite a few reasons. Don’t get me wrong, Hugo ain’t perfect, but having a little less JavaScript in my life has made me a happy chappy.
One thing that I’ve come to notice of late is that I’m a little different to a lot of developers that I meet. Many developers, seem to have a penchant for wanting to write code for the sake of writing code. To optimise, to agonise over, and ultimately to perfect the very specific piece of code that they’re working on, regardless of the bigger picture of the project.
I’m planning to write a little guide on how you can host a static site effectively, but it got me thinking that first I might wanna write about WHY you’d want to use a static site in the first place. Here goes!
After reading the recent reporting on the SQLite code of conduct I thought it might be fun to take a punt at a code of conduct based around the “Don’t be a Dick” philosophy. Should be fun!
Nothing is new, everything is rebooted, cloned, redone, reimagined and generally rehashed a million billion times until we stop noticing that it’s more of the same twaddle. Unfortunately, I quite like this domain so I figure that I’ll just stick with it now that I’m giving blogging another go :D