Kind bookmarks


With the recent news of increasing prices for organisers this is great to see the alternatives mapped out!

Recommended read: alternatives


Dominique shared this at DevOpsDays London, and it's a really great idea.

Because it can be difficult attending meetups on your own, Dominique and co have set up a community that makes it possible to meet folks before a meetup, maybe have a drink and a chat, and then head over together.

It has made a huge difference to folks wanting to attend, and has given people a lower barrier to attending an event, because they'll be able to chat to others on Slack before they go, so it won't be as awkward.

This is something that Tech Nottingham and Women in Tech Nottingham do, where before the event there will be some folks meeting at the Theatre Royal, and then they can walk over together, getting a chance to meet others.

Several of the organisers in the Nottingham tech scene chatted with Dominique about this at DevOpsDays, and we'll be looking to see if we can roll it out in Nottingham, too.

Anna has started to use her /events/ page as a way to help others see what events she's attending and for others to join her, too, and I think I'm going to be copying her and doing similar to make it easier for folks to see what upcoming events I'm attending.

Recommended read: Meetup Mates


This is a really interesting post to hear how some other folks in a similar environment to us manage their secrets.

It's always cool to see how other folks are doing similar things, anyway, and as usual, Monzo have a great blog post.

Recommended read: How our security team handle secrets


This is a great article on why we can't just let Google Chrome / Chromium take over the Web, and need to fight for other alternatives.

But as well as looking at the browsers, we need to look to the platforms too. If everyone ie uses Twitter, then Twitter are less likely to make changes because no one has an alternative. Whereas when we have multiple viable options, folks can jump around and use better platforms if they exist.

The IndieWeb is looking to do this - check out for a bit more info

Recommended read: The Web Can't Survive a Monoculture


This is very good news - open standards like OpenID Connect (OIDC) make interoperability and integration easier, so hats off to Apple!

Recommended read: Apple Successfully Implements OpenID Connect with Sign In with Apple


This is an interesting post, and is an important one to think about. We need to remember that although now we've got lax data privacy / retention laws, it's only going to get more user-focused and protect everyone more (which is universally a good thing!) but that we need to make sure we're architecting things in the right way to handle this.

Also, while you're thinking about this - have a read through some production logs and wonder "what could a bad actor do with these? Could they phish a customer? Could they steal their identity? Or are these so useless that we may as well not be logging anything at all?"

Recommended read: Logs were our lifeblood. Now they're our liability


Completely agree with this, as a meetup organiser, and would go one step further to say if you're able to RSVP if you're not coming that'd help too, otherwise there's the assumption you'll turn up, especially if you're a regular!

Recommended read: RSVP Rant


#10MoreBlogPosts sounds like a great initiative - hope that it'll help get more folks into blogging.

I've found it's really helped me personally since starting to work on blogumentation (blogging as a form of self-documentation )

Recommended read: Let’s write more blog posts: an experiment


I've just seen in my GitLab repo's issues that I've had an issue raised about my CI/CD configuration (

This seems like a great solution to try and find common issues in pipelines.

Recommended read: cd-linter


This is a great article about how to be safer when writing shell scripts. I am a huge proponent of not using them where possible, and instead moving them to another scripting language (Ruby, Python, Node) which you can test, and use a shared standard library.

Recommended read: Use the Unofficial Bash Strict Mode (Unless You Looove Debugging)


Justin talks us through the ability to retiring old systems being a really important capability for a company, making sure that it doesn't impact the users.

Recommended read: Rate of Successful Retire


This is a very interesting read - privacy and data ownership is quite familiar to those of us who have been using tech for some meaningful amount of our lives, but what about those who've never touched the Internet, but have suddenly found their data is being collected and owned by someone, somewhere?

Recommended read: Google Has My Dead Grandpa’s Data And He Never Used The Internet


This is quite an interesting little gotcha that many may not know (for instance I did not) about a 75GB limit of storage of Lambdas.

Recommended read: The Dark Side of AWS Lambda


I quite like this idea. As puts it, we should be comfortable with deploying no matter what day or time of the week, because our tooling and processes should give us confidence. It's an antipattern and a sign that something is wrong if we don't want to do it.

But at the same time, you don't want to be staying up late on a Friday because someone pushed something, and then have it potentially ruin your weekend.

It's definitely a hard line to walk, but as this article says, we should opt for something a bit more risky, to give us more confidence

Recommended read: Continuous Verification of Friday Deploys


I've been using DuckDuckGo for a couple of years now, and have no complaints. The privacy baked into the product is great, and their extensibility for things like !gh to search on GitHub or searching "html pretty print" is awesome for quick productivity boosting.

I'd recommend you giving it a go, and see how you feel after a while. And if you're finding search results aren't so great every so often, you can !g to get your Google results!

Recommended read: Bookmark of


This is a really great post about how we should look to use our time more wisely. Taking time to create something new instead of just consuming others' content, especially as you're all going to have some really interesting things to share.

However, we also need to remember that it's OK to have downtime, and consuming others' content is ok! (And yes, this is a little ironic coming from me, a person who is seemingly always productive and pushing out new content)!

Recommended read: Consume less, create more


This blog post from Monzo is such a good explanation of what the Strong Customer Authentication regulations are, especially coming from someone who's been working on it for some time. It's going to be interesting to see how the industry works at making it secure, but unobtrusive to the customer - as it's something that could cause quite a User Experience difficulty, at the risk of providing real security for our users.

Recommended read: Introducing Strong Customer Authentication: What you need to know


This is an interesting article about how the increased size of the Internet is a cautionary tale for whether things need to be on the Cloud / accessible from the Internet.

Recommended read: Absolute scale corrupts absolutely


This interview with George RR Martin is incredibly insightful into how George has been dealing with the TV series of Game of Thrones overtaking his literary pieces, and I'd really recommend a read to see his thought processes and the pros and cons of his writing being behind.

Recommended read: George RR Martin: 'Game of Thrones finishing is freeing, I’m at my own pace'


Readability of code is a very important, but so is using idiomatic language style. However the difficulty, as this article calls out, is that some folks won't find it easy to read or write code in an 'idiomatic' way. And also, who cares if you convert the readable four-line code snippet into a horrible to read one-liner? All it does is make it harder for the next person!

Recommended read: It's all Greek to me: Thoughts on code readability and aesthetics


This is a great read about some of the risks of using YAML, especially the way that most YAML parsers default to executing arbitrary, unsafe commands from a file you're parsing.

Recommended read: YAML: probably not so great after all


GitHub always have a great recap of the new Git releases, and this is another - I'm particularly interested in some of the changes around git checkout

Recommended read: Highlights from Git 2.23


This is another good article talking about the difficulties of working on the Web, with the plethora of technologies 'required' to get even a static website off the ground, let along big business applications. It's something we're all just accepting as a thing that happens (or folks from other tech stacks are ridiculing) but no one is really looking at what we can do to prevent it or make it better.

Recommended read: Let's talk about web education


This is a great post talking about some of the real difficulties of working in the Web ecosystem. It helps paint a picture of some problems that plague the folks working on it, and is a great view for someone who isn't as used to web development.

Recommended read: Why is modern web development so complicated? A long yet hasty explanation: Part 1!