Why a simple WordPress plugin edit broke everything
A client asked for one small change to a meme shortcode plugin, but its 2,000-line class made every edit risky. Splitting it by responsibility fixed that.
A client asked for one small change to a meme shortcode plugin, but its 2,000-line class made every edit risky. Splitting it by responsibility fixed that.
A tangled inventory plugin had hooks and direct class calls everywhere. Treating the WordPress Plugin API as the mediator, with hooks in a dedicated subscriber class, keeps the core logic clean and testable.
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…
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…
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 got a call from a client running a pretty complex WooCommerce store. Their shipping logic was a mess. They had all these rules for…
I got a call from a client running a decent-sized WooCommerce shop. They were in a panic. Their main shop page, which should have been…
Had a client call last week. They’ve got this huge, old WooCommerce plugin that’s been passed through three different dev teams. A new junior dev…
A junior dev on my team looked crushed. “They rejected my talk,” he said, staring at his laptop. He’d just gotten the canned ‘thanks but…
A client wanted a shortcode to highlight reader comments, but the inherited code crammed all the HTML into the shortcode function. Moving it into a dedicated generator class and a separate template file keeps the markup out of the PHP.