This article is about how I often invest time in ambitious projects just for the joy of working on the project, often without the intention of finishing or publishing the project. By the end of this article I hope you can see why investing your time in such projects is interesting and useful, so you can understand why I spend so much time on this, and why you might consider doing the same too.

This article explains how I solved a couple of challenges of getting my initial environment and configs into Git — the first steps to GitOps.

I’ve been wanting to embrace GitOps for quite some time, but it’s always tricky to know where to start. Do I use Jenkins Jobs — I know Jenkins well? It’s a bit old school though, maybe I should be using Ansible Tower. I’ve heard things about ArgoCD, and lots of others. The truth is, I can’t do anything until I actually have my environment and configuration stored in Git.

Speed up your command line navigation

Photo by Kevin Ku from Pexels

Knowing a few key shortcuts can have a surprising impact. As someone who sits frequently with others over a command line to help debug code and navigate servers, it’s easy to become frustrated on their behalf at how cumbersome things can be when you may not know time-saving shortcuts.

Here are some essential shortcuts and key tips to help you speed up your command line usage.

This article was written after 24 hours with a Mac Mini, i5 CPU, 8GB RAM, 1TB HDD. Mac OS Catalina. My own Monitor, Mouse, Keyboard.

What am I used to?

Been using Linux (Fedora, KDE) as my “daily desktop” for a longgg time now and 200% happy with it. It’s just perfect for me.

Windows. Have used everything Windows 95 up until Windows Vista as a “daily desktop”, then I switched to Linux. I’ve still used everything up to Windows 10, and I do have a Windows 10 laptop, but I only use as a games console.

We’ve all been there, you just want to hack up a quick Ansible playbook to do a quick task, and then you find yourself fighting with syntax, chopping and changing things around, wondering why this simple Ansible playbook isn’t working. Let me give you a few hints to make your life easier.

This is especially useful if you’re on a new machine that doesn’t come with all your personal configuration, dotfiles and preferred editors! This happens to me quite a lot when setting up new environments.