This is a resource I've used time and time again for getting straight-forward explanations of Free and Open Source licenses - I shared it in chat.indieweb.org the other day, so I thought I may as well share it here, too

This is a great post by David recounting the 'levels' of IndieWeb capabilities, in a way that makes more sense to those who haven't been as involved in the community, and want to know how to relate to more common points of reference, like social media.

I'm super excited for another chance to see Terence Eden speak! He's always brilliant, and most definitely knows his stuff.

Welcome to the IndieWeb, Craig! Glad to see it's helped you think about getting to self-publishing all your content, and I look forward to following you (once there's an RSS/h-feed set up!).

When I was promoting the last Homebrew Website Club on Twitter ( https://twitter.com/JamieTanna/status/1138339357121744897 ), a friend of Craig's tweeted to mention to him about it. We then spent a couple of days talking about it - and boom, Craig is now running his own Homebrew Website Club on 18th July ( https://getdoingthings.com/homebrew-website-club-barnsley-1/ ).

Last night Craig posted this great post about joining the community and with some great explanations for newbies. Welcome, Craig!

After the previous iteration of DevOps Nottingham died a death, it's exciting to see a new one starting again!

This is a really interesting read from Monzo about a recent incident they had. I really enjoy reading their incident management writeups because they show a tonne of detail, yet are stakeholder-friendly.

It's always interesting to see how other banks deal with issues like this, and what they would do to make things better next time.

This is a super interesting thread from Justin Garrison about the importance of words, using Disney as an example. It's always amazing to see examples of how these seemingly small changes can make huge differences.

This is a nice look back at the first year in Women in Tech York - great to hear and looking forward to many years to come!

As with 'You Guys', this is another great view into why using inclusive phrases are incredibly important.

This is one of those posts that sums up why the Nottingham tech community is so amazing - it's well worth a read, especially if you're not from Nottingham!

This is a great post by Jon about Firefox Containers and the power they can hold.

I lazily use them as a way to have i.e. multiple email accounts logged in, or at work having several AWS accounts logged in at once but have also got some pieces in place to containerise certain privacy-infringing companies' attempts to track me.

Unfortunately this clashes with the Women in Tech Takeover Digital Lincoln (https://www.meetup.com/digitallincoln/events/261313886/)

This will be the first time I'm attending Tech On Toast / TechFast, so I'm not looking forward to the early start, but Dan will make it worth it!

This is another post you really need to read, if you haven't already, as it makes you really think about the way you communicate.

I know a lot of people who use the term 'you guys' as a gender-neutral term, but after reading this article it really helps persuade you that the term is actually not as inclusive as you think.

For a couple of years now I've been making an effort to use gender-neutral ways to address groups, and I hope after reading this you will too.

As I've embraced indie post types, such as reposts, I've noticed that actually I've been using them wrong.

Looking at https://indieweb.org/bookmark#Repost it appears I've been conflating a "retweet" on Twitter with a "repost", thinking they were the same. Alas, they are not, and it makes more sense to be a bookmark.

I've since updated the posts using the wrong type and will get things right next time!

Being able to write semi-readable written text with technical terminology is a huge skill, and makes such a difference compared to not being able to write it.

I've found that since blogging more, my written language has gotten a lot better, and significantly makes my job easier.

I've worked with a number of brilliant engineers who can't explain themselves as well in written forms, which means commit messages and core pieces of documentation are difficult to understand.

Remember that you're never going to be the only person reading something, so make your content well thought out, re-read it and ask someone else to read through it to check it's OK.

Burnout sucks. There are a number of signs to pick up on it before it fully manifests which this article talks about. Having gone through it in the past, it's not something you want to go through, and can have some severely lasting effects that are hard to come back from.

Tell Him is a really important post by Jameela Jamil - if you don't read this, I'm incredibly disappointed in you

This is an incredible read about a huge undertaking the Guardian took to migrate two decades of content of migration with zero downtime - it's a great story and has a lot of great learnings in there