A better way to build complicated WordPress queries
I got a call from a client with a big WooCommerce store. Their “You Might Also Like” section on product pages was a disaster. It…
Tag: APIs
Stop writing messy WP_Query arrays. Do this instead.
Got a call from a client running a huge WooCommerce store. They wanted a “related products” feature that was… ambitious. It needed to show products…
Stop hooking your WordPress classes in the constructor
I got a call from a client in a panic. Their custom inventory sync plugin was failing silently on the live site. No errors, no…
Stop scattering WP_Query: use a repository pattern instead
I got a call from a client with a major headache. They run a big events portal, built on a custom plugin we inherited. Over…
WordPress OOP: are you over-engineering or just building it right?
A junior dev on my team asked for a code review last week. He was building a custom registration form for a client site, and…
My no-BS MacBook setup for WordPress development
A new junior dev joined my team last week, and I had to get them set up. I figured I’d just send them my list…
Stop chasing bugs with a better WordPress event management system
Had a client come to us with a site that was a total mess. It had years of custom code from different developers, and things…
How debugging skills make you a better developer
A WooCommerce coupon worked for regular customers but failed for wholesale ones. Deactivating plugins got me nowhere; stepping through the code with Xdebug found a role-check bug in about 15 minutes.
Importing WordPress data with the strategy pattern
A client needed to import users from a clean CSV and a messy pipe-delimited file. The strategy pattern kept the importer clean instead of a tangle of if/else blocks.
When a PHP loop is the wrong tool for the job
A WooCommerce sales widget kept timing out because it stacked nested foreach loops. Swapping them for array_filter, array_map, and array_reduce made the code fast and readable.