B: Foundational vis for rapid development

They're talking about setting up prebuilt templates and such that programmers can adapt to make something happen in a short amount of time. There is a trade off between simplicity and usability of a templating strategy. Someone mentions the Vega/trifacta model of a declarative language for data vis creation.

Tableau is another example. All of these languages tend toward being query languages over time.

If you're in a situation, like in a news room, where people have to crank out visuals every day, then you're going to want to have some kind of template or production strategy. You should build your flow such that the theme is consistent from visualization to visualization.

Someone mentions this visualization: http://rpgove.com/beermapping/

A lot of time the design process starts on paper.