> [!question] Lingering Questions > - Will the floated WebDevStudios contract-support arrangement materialize, and does it meaningfully change the maintenance picture for Custom Post Type UI and WP Search with Algolia? > - Is CPT UI's maintenance formally tied to WebDevStudios as an org, or was it in practice tied to Beckwith personally — and how would an outside user ever know the difference before a departure? > - How common is the FSE ramp difficulty he describes among senior WordPress backend developers, generally? His candor makes him visible, not necessarily unusual. > [!tip] Article Ideas > - "Plugin maintenance is person-shaped, not org-shaped" — use this case as the concrete anchor for a piece on supply-chain risk from single-maintainer dependency inside agency-owned plugins. (Needs a second case study to avoid over-generalizing from one post.) > [!link] Cross Reference > - [[3. Resources/Permanent Notes/Plugin Maintenance Attaches to a Person Not the Organization]] — the claim this note promotes > - [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] — maintenance capacity as a security property > [!quote] Vocabulary > - none — no specialized terms introduced beyond ordinary WordPress vocabulary (FSE, backend engineer) ## Bib capsule Michael Beckwith (tw2113), a 13-year WordPress backend engineer and maintainer of Custom Post Type UI and WP Search with Algolia, published a same-evening personal blog post announcing his separation from WebDevStudios after 13 years and 7 months, attributing it to a structural shift in the agency's work toward Full Site Editing rather than to performance, and asking his network for full-time remote WordPress leads. ## Author's thesis A long, well-regarded specialty can become non-viable inside an organization purely because the shape of the work changed — independent of whether the specialist's output quality declined — and the honest, undramatic way to handle that publicly is to name the gap plainly, credit the employer, and ask directly for help. ## Key arguments (≤3) 1. **Specialty demand evaporated without any decline in performance.** "The type of work within the scope of WordPress that we had has evolved, and the needs for my 'Backend Engineer' specialties had waned alongside that" — paired explicitly with "clients continuing to be happy with me." 2. **Thirteen years of WordPress experience did not produce FSE fluency.** An unusually candid admission from a senior developer, read as a curriculum signal rather than individual failing. 3. **Community-support labor is the proudest work and the least legible** to a hiring process — he leads with the support he gave CPT UI and WP Search with Algolia users, not with code shipped. ## Claim atoms ### Specialty demand can evaporate without any decline in performance > [!quote] ID:rw_mbwatch_h1 > The type of work within the scope of WordPress that we had has evolved, and the needs for my "Backend Engineer" specialties had waned alongside that. Where/why: the stated cause of separation, paired with "clients continuing to be happy with me. So, nothing that I did wrong" — displacement framed as structural, carefully separated from work quality. ### Thirteen years of WordPress experience did not produce FSE fluency > [!quote] ID:rw_mbwatch_h2 > I never fully grasped how to best, and efficiently, work with Full Site Editing for example. I also struggled with the evolving tools sets that were being used and praised. Where/why: an unusually candid public admission from a senior developer — read as evidence the existing FSE learning path doesn't reliably carry experienced classic-PHP developers across, not as an individual shortcoming. ### Community support labor is the proudest work and the least legible > [!quote] ID:rw_mbwatch_h3 > I am also proud of the multitudes of community support that I was allowed to provide for WebDevStudios' products like Custom Post Type UI and WP Search with Algolia along with their premium counterparts. Where/why: he leads with support work, not code, when naming what he's proud of — that labor is highly visible to users and nearly invisible to hiring processes. ## Permanent candidates - **P1 — Plugin maintenance attaches to a person, not the organization that owns it.** Strong candidate: an agency may own a plugin, but its support capacity usually lives in one individual, so a single departure can degrade maintenance for every dependent site with no ownership change to signal the risk. Promoted below. ## Processing checklist - [x] Port claim atoms and permanent candidate from the existing deep-read notes field - [ ] Watch CPT UI and WP Search with Algolia support-thread response times over the following 90 days as a continuity signal - [x] Connect into the relevant MOC — [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] ## Links - [[3. Resources/MOCs/WordPress Hosting Security Stack MOC]] — maintainer continuity as a supply-chain/security property, not only a career story - [[3. Resources/Readwise/Full Document Contents/Articles/And now my watch has ended]] — source document