Why ‘write more code’ is terrible advice for developers
A client WooCommerce checkout kept throwing a random fatal error. The fix was not more code, it was reading the core files first. Why reading code beats writing more of it.
A client WooCommerce checkout kept throwing a random fatal error. The fix was not more code, it was reading the core files first. Why reading code beats writing more of it.
A plugin stuffed 2MB of logs into one autoloaded option and dragged every page down. Here is how the Options API autoload flag works and how to split the data properly.
Hooks buried in class constructors made a WooCommerce plugin impossible to follow. Here is how a small PHP interface and a hook manager give every class a clear, testable contract.
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’s site kept redirecting to a pharma store no matter how many times they cleaned it. The malware was only the symptom; an outdated plugin left a backdoor open.
I got a call about a membership site that was, for lack of a better term, freaking out. Logged-in users were seeing the public, logged-out…
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…