A fun distraction occurred this week when the following snippet of bash code was suggested in a pull request (simplified for demonstrative clarity):
1if [ echo $VAR1 | grep -q "text" ] || [ $VAR2 -eq 0 ]; then 2 echo "If test passed." 3else 4 echo "If test failed." 5fi Taken at initial face value, it looked like it should work okay. There didn’t appear to be anything immediately wrong with its syntax.
In this blog we’re going to learn how we can use kubectl’s patch command to modify the configuration of Kubernetes-managed resources via the command-line. Before we do that though, we’ll go through a quick primer on how you can display Kubernetes resources so that you know what and where to patch.
Getting Kuberenetes resources One of the first kubectl commands a Kubernetes beginner will become intimately acquainted with is the get command.
In the previous blog I described why Advent of Code is an awesome and creative way to exercise your programming skills. A few days ago I wrapped up 2019’s problems, although I must admit I needed some serious help (read: reading someone else’s solution) to do Day 22 Part 2.
This year was also the first year that I managed to convince some work colleagues to join me on the AoC train, which made for some fun watercooler discussions in the morning where we could talk about the ways we solved (or got stuck) on the previous day’s problem.
Why AoC? I’ve long wanted to write a blog promoting the merits of Advent of Code and - since it has just wrapped up its fifth year - there seems to be no better time like the present.
Advent of Code (or AoC as I’ll refer to it hereafter) is a solo effort by Eric Wastl. Commencing each year on December 1st, it presents an advent calendar-style series of daily programming challenges in the lead-up to Christmas.
It’s the end of the year, so I figured I’d kick this blog off by highlighting the excellent work of other authors’ blogs, articles and long-reads which I enjoyed through the year. This is by no means a comprehensive list - I’m just going through things in my Instapaper account, which is largely just stuff I thought to archive rather than delete once I’d read it. And, there’s an obvious technology bias towards the content.