Avoiding Go runtime errors with interface compliance and type assertion checks
As I've been brushing up on my Go skills with a side project, one question I had was how errors related to structs not implementing an interface manifest in different ways in Go. So here's a bit of a dive into what I learned on how
How to install nvim-ufo in LazyVim to enable foldable code blocks
A feature that I've found myself missing since making the switch to Vim as my editor of choice is the ability to easily fold and expand code blocks. I know this functionality is included in Neovim, but I couldn't understand the native implementation enough to use

What is a carbon handprint?
I've recently started reading "Building Green Software" as part of an online book club and, in the introduction, the authors reference the potential "carbon handprint" of software. I wasn't familiar with this term, so I decided to dig into it to learn

Git Log's Hidden Gems: Using -S and -L for Powerful Code History Search
Ever needed to track down when a specific piece of code was first introduced in a project? As part of some refactoring I had to do recently, I needed to do just that for a variable on a Django model. I was already familiar with the basic git log command,
