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:
YAML: probably not so great after all
This is a great read about some of the risks of using YAML, especially the way that most YAML parsers default to executing arbitrary, unsafe commands from a file you're parsing.
Recommended read: YAML: probably not so great after all https://arp242.net/yaml-config.html
by 
Jamie Tanna
.
#yaml.
I've used this server before to get a simple RESTful API up and running, and it's really useful.
Recommended read: JSON Server https://github.com/typicode/json-server/
by Jamie Tanna
.
#tools
#rest.
GitHub always have a great recap of the new Git releases, and this is another - I'm particularly interested in some of the changes around git checkout
Recommended read: Highlights from Git 2.23 https://github.blog/2019-08-16-highlights-from-git-2-23/
by Jamie Tanna
.
#git.
I will be attending September Double Whammy - Noobs on Ubs and the IndieWeb on
by Jamie Tanna
.
#phpminds.
Let's talk about web education
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.
Recommended read: Let's talk about web education https://getdoingthings.com/blog/lets-talk-about-web-education/
by Jamie Tanna
.
I will be attending Alexa.Net with Steve Pears + Writing Business Apps in F# with Ian Russell on
by Jamie Tanna
.
Why is modern web development so complicated? A long yet hasty explanation: Part 1!
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.
Recommended read: Why is modern web development so complicated? A long yet hasty explanation: Part 1! https://www.vrk.dev/2019/07/11/why-is-modern-web-development-so-complicated-a-long-yet-hasty-explanation-part-1/
by Jamie Tanna
.
Bookmark of Jessie Frazelle's tweet about the origins of the Apache Web Server's name
Recommended read: Bookmark of Jessie Frazelle's tweet about the origins of the Apache Web Server's name https://twitter.com/jessfraz/status/1096487290795450369
by Jamie Tanna
.
Effective API testing with Cucumber
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.
Recommended read: Effective API testing with Cucumber https://www.gregbeech.com/2014/01/19/effective-api-testing-with-cucumber/
by Jamie Tanna
.
#cucumber
#testing.
Why Community Matters by Digital Lincoln
Recommended read: Why Community Matters by Digital Lincoln https://medium.com/dddeastmidlands/why-community-matters-by-digital-lincoln-3e34c71a57ef
by Jamie Tanna
.
I will be attending Homebrew Website Club Nottingham on
I will be attending Homebrew Website Club Nottingham on
Learn a little jq, awk and sed
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.
Recommended read: Learn a little jq, awk and sed https://letterstoanewdeveloper.com/2019/07/29/learn-a-little-jq-awk-and-sed/
by Jamie Tanna
.
#command-line.
I will be attending Tech Nottingham August 2019: Caching and Documenting on
by Jamie Tanna
.
#tech-nottingham.