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…
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…
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…
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…
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.
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.
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.
Editing one English button label broke the German, French, and Spanish translations. Using stable keys as placeholders, plus an en_US fallback, keeps that from happening.
A one-line shipping tweak would have broken inventory reporting and a homepage shortcode. Tight coupling and low cohesion are why, and here’s how to structure the code instead.
I was working on a WooCommerce plugin for a client to sync their product inventory with a third-party API. Total classic scenario. The problem was,…
I got a call from a client running a pretty complex WooCommerce store. Their shipping logic was a mess. They had all these rules for…