We need to talk about the specialist obsession. Somewhere along the way, the standard advice for scaling WordPress teams became hire for hyper-depth: the dev who only does React hooks, the one who only touches Nginx configs. On real sites, the ones with broken checkouts and a decade of legacy code, that approach kills productivity. What those teams need is the Data Generalist mindset, someone who follows the whole flow and uses range to catch what specialists walk past.
WordPress is a wicked learning environment
Most development tutorials assume a kind learning environment: a closed system with clear rules and instant feedback. A live WooCommerce site with 50+ plugins, a custom theme and 14 years of technical debt is not that. David Epstein calls it a wicked learning environment, a place where patterns do not repeat and doing the correct thing breaks something unrelated.
This is where the Data Generalist earns their money. A specialist can spend hours tuning one SQL query while the actual bottleneck is a race condition in a sloppy transient. In a wicked environment, picking the problem worth solving is harder than solving it.
AI is the new specialist layer
Deep specialization used to be a moat. AI has drained most of it. ChatGPT and Claude work as on-demand specialists: a gnarly regex, a function refactored into a specific design pattern, a custom Nginx rule, all in seconds. They are frighteningly good at the how.
So the value of a human developer has moved toward coordination. I have written about how WordPress AI plugin development is reshaping our workflows. Much of the job now is navigating ambiguity. The Data Generalist is the one deciding when to trust the AI’s specialist output and when experience says to throw the strategy out and start over.
The coordination tax
In a lot of organizations, the two-pizza team turned into a coordination problem. Every specialist you add is another relationship somebody has to manage, and every small change gets more expensive to make. A generalist ranges across those silos. They do not need a meeting between the database guy and the front-end guy, because they already know how the two connect.
“Generalists are no longer just connectors; they are the ones navigating environments where the path forward isn’t obvious.”
Range over depth sits at the center of pragmatic WordPress development. Ship the thing that grows revenue and keeps customers happy instead of arguing over whether it used the newest agentic model or one well-placed SQL query. The business does not care which one you reached for.
If this Data Generalist work is eating your dev hours, hand it to me. I have been wrestling with WordPress since the 4.x days.
How to widen your range
Hyper-specialization has not disappeared, it is being pushed to the edges. To stay useful as a developer, stop behaving like a single-function tool and start behaving like a system navigator. The reflection on generalists that kicked off this argument puts the value in connecting people and capabilities. Let AI take the specialist tasks and spend your own “range” on the parts that stay messy.
