IndieWeb post types

This should be a really interesting listen about getting started with the IndieWeb with David, I'd recommend it.

But in an even cooler turn of events, it was very cool to see that my article Why I Have a Website and You Should Too ( https://www.jvt.me/posts/2019/07/22/why-website/ ) discussed at roughly 39:00.

This is a really interest post about the dangers of installing work apps (such as email) on your personal device. This is something I've spent a lot of effort avoiding in the last couple of jobs, as well as going out of my way to not use any personal services (i.e. social media, email) on my work devices, as there is most likely traffic inspection or they are Man-in-the-Middle'ing the traffic, and will therefore be able to glean passwords. Although this seems paranoid, I feel it's a good mindset to have.

This is especially useful because it has a great way of enforcing the separation between home and work. However, there are still ways that this can break down - for instance, I have a work phone which is provided so I can be out of hours on call. However, I have things like email and Slack which allow me to use it throughout the day and reply to messages when I'm not necessarily with my laptop. But that's an issue because that phone goes home with me, even when I'm not on call. I'll find I'm catching up on work on the bus on the way to work, as well as keep in the mindset of work when I'm physically out of the building.

This makes it quite difficult because I'm not really switching off, even though I've said above that I'm trying to keep work and home separate. So what I've been doing for the last few months is leave my work phone at work (as long as I'm not on call!) which means if I've left the office, I'm no longer able to action anything, even if I think about it.

This is another interesting article about automation, and how it slowly incurs time costs by waiting for the right time to properly tackle the automation, rather than piece-by-piece.

This is a really interesting way of approaching automation in a gradual way - make the documentation in code, then take that code and slowly iterate over it until you have a fully automated solution. I like it - obviously we always want to have the final product, but it's a good way to get there slowly

This is a great post by Shubheksha and talking about the right way to talk about production issues.

Having a blameless culture makes it easier for new/junior engineers getting started with working on production systems, and makes everyone more comfortable working on things where they know they won't get the blame pointed at them.

I've found that, at work, diagnosing issues in our staging environment has given me such a great experience - it's been great to practice dealing with production-like issues in a non-production environment, as it gives you that time to breath, experiment and learn, as well as giving me much greater understanding of the end-to-end system.

This is going to be a very interesting talk - there is so much of this around (I'm guilty too) and it'll be good to hear some more about it from James Seconde

As I've said before, I'm a big fan of how Monzo handles their production incidents because it's quite polished and transparent

This is a really interesting post. Only the other day, Anna and I had been talking about how it'd be interesting to work 4 days a week, or even part time. It sounds like it'd be a great opportunity if you're able to financially cover it

Exciting to have another meetup re-start, as well as this being a very interesting topic

This is a really interesting article about the flaws in PGP - I don't have enough security backing and understanding to argue it, but it sounds legitimate. It's a surprise this isn't being talked about more if it is as bad as it is

Unfortunately I won't be able to make it as Anna and I have plans that night - but please do go ahead and meet!

I've decided to attend Homebrew Website Club instead