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.

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.

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?

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.

I quite like this idea. As https://charity.wtf 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

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!

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)!

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.

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.

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.

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!

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.

I've used this server before to get a simple RESTful API up and running, and it's really useful.

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