In my desire to create a better process for building and deploying at Zeek, I recently hit a road bump while trying to perform automatic visual regression testing immediately after deployment.

Purpose

Automatically load all PHP files in the specified directory. Recursively.

It’s nice to pre-populate terms, content or have the ability to only OCCASIONALLY run actions.

Make your code simpler to read and simpler to debug by breaking apart your conditional statements and exiting the function whenever possible.

Did you know you can not only use Composer to manage dependencies, but actually develop a package alongside your dependencies?

What are subtrees, why are they useful and how can they be used?

When working with caching strategies, it’s important to step through your invalidation strategies. Namely, thinking through at what point does the data that you’re caching get regenerated, how does it get regenerated and who is regenerating it. It could be regenerated any time a new post is published, on a save_post hook by an author or admin OR it might need to be regenerated every 15 minutes by anyone hitting the front page.

Recently I ran into an issue where an installation of WordPress that had never had any issues updating stopped being able to update via the admin update button.

One of the lowest hanging fruits to learn is how to fix code regressions quickly and easily with git bisect.

This was a fun little issue to come across - I’ve been using Nginx as my local development server and so far have had few complications, however anytime I went to upload an image I would get a very vague HTTP Error from WordPress.