EI-5.2 — Flagship Editorial Review

Status: COMPLETE
Date: 2026-08-08
Baseline: 7128ff360badf9758f5520e1de029179c07b48d1

Objective

Perform a second-pass editorial review of the highest-priority retained pieces identified by EI-5.1. This is not another migration rewrite. The purpose is to decide whether the already-restored pieces are strong enough to remain flagship material and whether any further substantive rewriting is justified.

Flagship set reviewed

1. A programmer, again
2. The Age of Marvels
3. Twenty-thirteen
4. Why IT support is hated

All four already carry canonical content_type: writing, canonical subjects, historical provenance, explicit original dates, revision dates, and stable permalinks.

Editorial decisions

A programmer, again — KEEP AS FLAGSHIP

Current metadata: Technology; featured; importance 5.

The piece has a strong career arc: first paid programming work in 1983, journalism as an intervening career, programming returning through the web, formal study, and paid iPhone development thirty years later. The closing sentence connects directly to the site’s current identity: learning systems, making useful things, and continuing to learn.

Decision: No second rewrite. The EI-3.4 version is concise, coherent, and central to the professional narrative. Additional expansion would weaken the circular structure.

The Age of Marvels — KEEP AS FLAGSHIP

Current metadata: Computing History; featured; importance 5.

The surviving magazine memory is now framed around scarcity of computer knowledge and the experience of learning from magazines, manuals, listings, and conversations before searchable information became ubiquitous. The recovered ComputerGlossary.jpg gives the piece a concrete historical artifact rather than generic nostalgia.

Decision: No second rewrite. Preserve the current prose and recovered scan. It is one of the clearest bridges between personal memory and computing history in the retained corpus.

Twenty-thirteen — KEEP FEATURED, SECONDARY FLAGSHIP

Current metadata: Computing History; featured; importance 4.

The piece is intentionally small. Its value is the specific memory of computer ID 2013 and the early discovery that a computer could be investigated beyond its intended lesson path. The final line gives the anecdote a durable connection to later technical curiosity.

Decision: No expansion. Treat its brevity as a strength. It supports the larger computing-origin narrative without duplicating A programmer, again.

Why IT support is hated — KEEP FEATURED, SECONDARY FLAGSHIP

Current metadata: Technology; featured; importance 4.

The Blackboard/browser story remains readable because it is a troubleshooting story rather than a claim about current browser technology. The revised ending explicitly acknowledges that the browsers are historical while preserving the support lesson.

Decision: No second rewrite. The piece should remain compact and humorous. Modernizing the software references would damage the historical anecdote.

Cross-corpus finding

The four pieces work best as two paired narratives:

• Learning to investigate systems: Twenty-thirteen → A programmer, again
• Technology across time: The Age of Marvels → Why IT support is hated

These relationships should be implemented during EI-5.4 contextual linking rather than by adding explanatory paragraphs to the articles themselves.

Featured judgment

The current importance split is editorially defensible:

• importance 5: A programmer, again; The Age of Marvels
• importance 4: Twenty-thirteen; Why IT support is hated

EI-5.5 should review these values against the entire featured corpus, but EI-5.2 finds no reason to demote any of the four.

Preservation constraints

• Original publication dates remain authoritative.
• Stable permalinks remain unchanged.
• Revision provenance remains visible.
• Recovered historical media remains local production media under EI-2 governance.
• No private/DELETE material is introduced as context, evidence, related content, or media.

Result

EI-5.2 closes with zero additional prose rewrites. That is an editorial decision, not an omission: the highest-priority EI-5.1 pieces survived second-pass review without needing further rewriting.

The next work should move to the secondary development queue rather than repeatedly polishing already-coherent flagship pieces.

Next sprint: EI-5.3 — Secondary Editorial Review.