# Abstracting Drudgery Re-Opens Creative Work to Non-Specialists ## Claim Each time tooling abstracts away technical drudgery, it temporarily re-opens creative work to non-specialists before the next specialization wave narrows it again. <!-- atomicity: 1 idea ✓ --> ## Evidence **Source**: [Jake Goldman — AI Brings Back Web Dev's Golden Era](https://read.readwise.io/read/01kvg9xpyrxtppc08s1bswbvjp) > [!quote] > "when did we turn CSS into a programming language right with variables" Goldman's "golden era" argument: the early web let creative, lightly-technical people do good work; then over-specialization (CSS-as-programming-language, deep toolchains ~2013–14) narrowed the field to specialists. He claims AI removes syntax as the bottleneck ("very little handwritten code"), re-opening the door — the same pattern as desktop publishing, spreadsheets, and no-code before it. Read as a *cycle*, not an endpoint: abstraction widens access, then new specializations (now: prompting, context, orchestration, "treat AI like a worker") re-form around the new layer. ## Scope & conditions - Holds for creative-technical crafts where a tooling layer can hide the previously gatekeeping skill (typesetting, web design, coding). - The "re-opening" is temporary and partial; it is also a self-interested optimism when voiced by someone (agency owner) who profits from the new wave — treat the cycle as the durable claim, the "golden era" framing as contingent. ## Links - [[3. Resources/Permanent Notes/Zero Build Cost Shifts Advantage From Depth to Breadth]] — extends: removing implementation drudgery lowers the cost of each additional capability and makes broad functional coverage strategically possible - [[3. Resources/Permanent Notes/Template-Presence Is the Diagnostic of Automatability]] — applies-in: patterned, templated steps are the drudgery AI can remove while leaving the non-templated creative judgment to the person - [[3. Resources/Permanent Notes/Implementation Is Cheap So Taste Becomes the Bottleneck]] — extends: abstraction removes implementation labor, leaving selection and aesthetic judgment as the scarce differentiator. - [[AI Capability in a Domain Advances Through a Fixed Three-Stage Arc]] — evidence-for: the assist-to-autonomy arc describes how generalized capability progressively removes specialist execution barriers. - [[AI Is a Building Block You Build From Not a Tool You Add to a Workflow]] — extends: once drudgery is abstracted, non-specialists can design work around AI as a material instead of adding it to an expert workflow. - [[The Bottleneck Moved From Code Generation to Review and Judgment]] — extends — names the *new* specialization that re-forms after AI abstracts syntax: review/judgment becomes the scarce skill - [[AI & the Future of Knowledge Work MOC]] — applies-in — the labor-and-skill shift AI drives across creative work - [[Concentration Beats Coverage Under Retrieval]] — contrasts — a different AI-era dynamic (retrieval) from the same week's reading; both reshape what skill is scarce - [[3. Resources/Permanent Notes/AI Tools Don't Eliminate the Apprenticeship Layer They Relocate Its Cost]] — contrasts: that note argues the *formation* work AI removes has to reappear elsewhere; this note argues the *access* AI opens is itself cyclical and will re-narrow ## Tests / falsifiers - Track whether prompt/context engineering calcifies into its own specialized discipline within a few years, the way CSS did — if it does on the same timeline, the cycle claim holds; if access stays durably wide, the claim is wrong or the mechanism differs this time. - Compare who ships production work in the AI-coding era (formerly-locked-out generalists vs. the same specialist population using new tools) — if it's mostly the same specialists just working faster, the "re-opens access" half of the claim fails. ## Implications - For WordPress agencies: the re-opening expands the market (more people can build) while moving the agency's value to architecture/orchestration/accountability. - Open question: is each abstraction-then-respecialization cycle shorter than the last, and does that compress careers built on the transient "open" window?