IndieWeb post types

This content type is full of IndieWeb post types, which are all content types which allow me to take greater ownership of my own data. These are likely unrelated to my blog posts. You can find a better breakdown by actual post kind below:

 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!

 Bookmark

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.