Field perspectives
These sources expose purposes and production constraints that benchmarks omit. Most are first-person cases, interviews, or essays: they establish that a perspective or experience exists, not how common or effective it is.
Two current newsroom diaries describe work that once took weeks appearing in days or hours.
They also contain wrong totals, broken geography, missed notes, repeated correction, usage limits, mobile checks, and new validation work. Benn Stancil explains why a plausible chart cannot validate its calculation.
Semantic stakes, independence of the check, cost of error, and ownership of the complete pipeline.
Enrico Bertini maps opportunities across data acquisition, wrangling, analysis, tours, and creative exploration. Alberto Cairo treats easier code as capacity extension.
Question quality, interpretation, and final analytical choice become more important. Exploratory, explanatory, essayistic, and artistic work do not share one quality function.
Purpose, audience, consequence, capability profile, and whether the claim remains inspectable.
Removing syntax and formatting work can get a person to a candidate before the question goes cold.
A classroom exercise used failed prompting to reveal missing chart structure. An analog practice made slowness a source of attention, experimentation, and care.
Whether the effort is obsolete mechanics or practice in structure, skepticism, memory, and meaning.
Generated descriptions and alternatives may help newsrooms address access at a scale that manual workflows have not reached.
Elavsky and Xiong Bearfield show model chains losing data, source, uncertainty, design, and purpose. Blind journalist Johny Cassidy describes an organizational and multimodal problem, not an alt-text checkbox.
Whether the reader can test the account, choose another modality, report failure, and obtain remediation.
Richard Brath asks which charts remain useful when models extract insights. Elijah Meeks proposes audience, intent, interpretation, and conversation as framework objects.
Domestic Data Streamers argues that visualization remains a distinct language for comparison, human experience, and creative divergence.
Reader task, need for overview or shared evidence, qualitative meaning, novelty, and an auditable interaction trace.
Production cases
Both are self-reports by the people who built and checked their own projects. Keeping the gain beside the incurred work prevents “built in a week” from becoming a quality claim.
One map fell from roughly three weeks in 2012 to a two-day reconstruction.
A recognizable site appeared in about an hour; the full dashboard and checking workflow took one week.
An equal-budget comparison with the best current direct workflow or another practitioner.
Incorrect totals and incomplete bilingual text required source comparison and repeated correction.
Cities rendered in the sea or broken shapes; exact evidence and source notes were sometimes missed.
A field distribution of error, correction time, regression, premature acceptance, or abandonment.
About 20 ordered tasks, source checks, and open code made components easier to trace and revisit.
Extraction, data, presentation, insights, and fact-checking were separated so repairs could be replayed.
That decomposition or a model-built validator independently improves correctness across projects.
Working prototypes were published; attention, understanding, and civic use remained the stated bottleneck.
Mobile rendering was checked and stakeholders reacted; readers were not tested.
Audience understanding, accessibility, consequential use, or sustained adoption.
Record reconciliation and scheduled updates were proposed next steps.
Refactoring and longer-term maintenance remained after the one-week build.
Later refreshes, dependency changes, second-person handoff, incident response, or retirement.
Ottaviani build diary ↗ · Tordecilla build diary ↗. These cases support process claims, not general productivity or accuracy estimates.