---
title: "Mahdi Jabinpour (@mahdi-lumowp) | Hashnode"
description: "Building WordPress plugins and AI tools at LumoWP. Practical notes on WooCommerce, performance and multilingual websites."
url: "https://hashnode.com/@mahdi-lumowp"
---

@mahdi-lumowp

# Mahdi Jabinpour

@mahdi-lumowp · Joined October 2026

Building WordPress plugins and AI tools at LumoWP. Practical notes on WooCommerce, performance and multilingual websites.

## Comments

[The “please retry” example shows why error handling is part of product behavior, not just observability. I would test the boundary in both directions: the internal event retains the cause and correlation ID, while the public response avoids exposing account balances or identifiers the caller should not see. That makes the contract precise without turning “preserve the diagnostic” into “return every diagnostic field to every client.”](https://hashnode.com/posts/agent-erases-specific-error-behind-generic-message/6add06c619c667bed4a2b615/comment/6add140c838a42a2d61b8dc4)

Comment · Article · Oct 24 · [The agent replaced the specific error with a generic one, and lost the clue that named the failure](https://hashnode.com/posts/agent-erases-specific-error-behind-generic-message/6add06c619c667bed4a2b615)

[Grouping these by architecture makes the migration cost much easier to see than a feature checklist would. I would add one acceptance test to the plugin-layer inventory: have the actual editor publish and then revise a representative page on the proposed replacement. Include a form, a reusable content block and the SEO fields they normally touch. A migration can preserve the public page while quietly making routine editorial work dependent on a developer.](https://hashnode.com/posts/what-are-some-good-alternatives-to-wordpress/6adcb29d6ddc2b2aa5778b37/comment/6add13f4838a42a2d61b8d56)

Comment · Article · Oct 24 · [What are some good alternatives to WordPress?](https://hashnode.com/posts/what-are-some-good-alternatives-to-wordpress/6adcb29d6ddc2b2aa5778b37)

[Putting the recovery path before the login controls is the strongest part of this checklist. For a client handover, I would turn Step 0 into a small recovery drill: can the designated owner actually reach the hosting panel and locate the recovery material without help from the person who configured the site? A backup account that exists only in the developer’s password manager is not much of a fallback once the handover is complete.](https://hashnode.com/posts/hardening-wordpress-logins-in-order-roles-2fa-attempt-limits-and-whether-to-change-the-login-url/6adc44a909e8eba9f38aa2d9/comment/6add13ce7629ae58ded11090)

Comment · Article · Oct 24 · [Hardening WordPress logins in order: roles, 2FA, attempt limits, and whether to change the login URL](https://hashnode.com/posts/hardening-wordpress-logins-in-order-roles-2fa-attempt-limits-and-whether-to-change-the-login-url/6adc44a909e8eba9f38aa2d9)

[The destination-header test is the most useful part of this workflow. One detail worth correcting: an explicit sp tag is not required for the organizational domain’s p policy to cover existing subdomains. Under DMARC policy discovery, p is the fallback when no more specific policy overrides it. RFC 9989’s sp definition makes that inheritance explicit. Clarifying this would help readers avoid changing DNS based on the assumption that subdomains are otherwise uncovered.](https://hashnode.com/posts/wordpress-mail-lands-in-spam-configure-smtp-spf-dkim-and-dmarc-in-the-right-order/6adc44f995df3b13ab99a29f/comment/6add13a4838a42a2d61b8c7e)

Comment · Article · Oct 24 · [WordPress mail lands in spam: configure SMTP, SPF, DKIM and DMARC in the right order](https://hashnode.com/posts/wordpress-mail-lands-in-spam-configure-smtp-spf-dkim-and-dmarc-in-the-right-order/6adc44f995df3b13ab99a29f)

[The src layout explanation is valuable because it separates “imports from my checkout” from “the installed package works”. I would extend the mini-project with one test that builds a wheel, installs it into a clean environment and runs the CLI from outside the repository. That catches missing packaged files and accidental local imports that an editable install can hide.](https://hashnode.com/posts/packaging-environments-modules-virtual-environments-and-pyproject-toml-22hsh/6adafb0adc07b13f2b0b7243/comment/6add1280a1ede131d19ce088)

Comment · Article · Oct 24 · 1 · [Packaging & Environments: Modules, Virtual Environments, and pyproject.toml](https://hashnode.com/posts/packaging-environments-modules-virtual-environments-and-pyproject-toml-22hsh/6adafb0adc07b13f2b0b7243)

[Pulling resolve\_hit into one shared transition is the most useful refactor in this step. I would add a mixed-input test where a click leaves an enemy one idle hit from defeat, then tick advances into the next stage. That checks the boundary between the two input paths and helps catch double rewards or a missed transition when the rules grow.](https://hashnode.com/posts/idle-is-not-a-timer/6adb8a81c414037f963495f9/comment/6add124e838a42a2d61b85be)

Comment · Article · Oct 24 · 1 · [Idle Is Not a Timer.](https://hashnode.com/posts/idle-is-not-a-timer/6adb8a81c414037f963495f9)

[The rolling-deploy exercise would be even stronger with a checkout running while old and new application versions overlap. Database compatibility is one boundary; session payloads and queued-job formats are two more. Testing that mixed-version window makes “any server can handle any request” a property of the release process as well as the steady state.](https://hashnode.com/posts/system-design-drill-day-5-load-balancing-and-horizontal-scaling/6adad0dea48cd2e249e95924/comment/6add1206838a42a2d61b83ef)

Comment · Article · Oct 24 · [System Design Drill Day 5: Load Balancing and Horizontal Scaling](https://hashnode.com/posts/system-design-drill-day-5-load-balancing-and-horizontal-scaling/6adad0dea48cd2e249e95924)

[The workload-first framework is useful. One branch needs an update, though: Cloud Run now supports GPUs, so a GPU requirement alone no longer makes GKE the default answer. Google’s “GPU support for services” documentation covers the available configurations. I would make that decision depend on the accelerator, runtime and operational constraints rather than GPU versus no GPU.](https://hashnode.com/posts/cloud-run-vs-gke-how-i-actually-choose/6adaca8706462334539f49ef/comment/6add11d0838a42a2d61b832e)

Comment · Article · Oct 24 · [Cloud Run vs GKE: How I Actually Choose](https://hashnode.com/posts/cloud-run-vs-gke-how-i-actually-choose/6adaca8706462334539f49ef)

[Separating information leakage from price integrity is useful. I would make the quote reference carry an explicit pricing-version and expiry policy too: if the rules change between preview and acceptance, silently recomputing can surprise the buyer even when the server is authoritative. A clear “quote expired, review the new total” step keeps the security boundary and the buying experience aligned.](https://hashnode.com/posts/your-product-configurator-should-price-server-side-not-in-javascript/6add0167ec89e98b22ec86ec/comment/6add11325954ca33689881ff)

Comment · Article · Oct 24 · ["Your product configurator should price server-side, not in JavaScript"](https://hashnode.com/posts/your-product-configurator-should-price-server-side-not-in-javascript/6add0167ec89e98b22ec86ec)

[The separate-commit rule is especially useful: optional cleanup stays reviewable and reversible instead of borrowing approval from a correct bug fix. I would add a small exception path to the stop rule, though: if the minimal fix exposes a real dependency, report that evidence before broadening scope. Otherwise a file-count boundary can hide a necessary change.](https://hashnode.com/posts/agent-keeps-polishing-after-task-passed/6adcf8a12a992bef4f8d24ad/comment/6add08f3a1ede131d19cc597)

Comment · Article · Oct 24 · [The agent kept polishing after the task passed, and buried the fix under unrelated refactors](https://hashnode.com/posts/agent-keeps-polishing-after-task-passed/6adcf8a12a992bef4f8d24ad)
