Kind bookmarks

 Bookmark

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.

 Bookmark

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 https://indieweb.org/why for a bit more info

 Bookmark

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?"

 Bookmark

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?

 Bookmark

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

 Bookmark

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!

 Bookmark

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

 Bookmark

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.

 Bookmark

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!