IndieWeb post types

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.

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.

This post has definitely helped my recent scenario writing, and helped to shape the readability (and purpose) of the Cucumber testing I've been doing.

This is a great post - I thoroughly recommend learning how to use common commandline tools such as awk, grep, sed, but also adopting a scripting language for more complicated stuff. I don't mean Bash, or another shell scripting language, but something like Node, Python or Ruby, as it'll give you the opportunity for a greater standard library, as well as tonnes of packages built by others.

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