PUBLIC MARKS with search rules

I like to compare this practice to a game designer who lays out an intended context, rules and narrative for the game, but then has this moment of delight when users engender their own narrative, their own path. This is intrinsic to the conception of Information Visualization as a discovery tool.

API designers, please note the following rules before calling your creation a REST API:

Web app developers spend most of our time not thinking about how data is actually transmitted through the bowels of the network stack. Abstractions at the application layer let us pretend that networks read and write whole messages as smooth streams of bytes. Generally this is a good thing. But knowing what's going underneath is crucial to performance tuning and application design. The character of our users' internet connections is changing and some of the rules of thumb we rely on may need to be revised.

We were able to come up with rules that make using prefixes in almost any context simpler. Note, these are for the most part AUTHORING guidelines, not requirements when reading:

1. Reusing the same prefix in the same document with different meanings is horribly confusing (”If you did that, I’d break your figures.”). Possible to figure out, but not really desirable. Seems like a reasonable place for a warning.

2. Defining all the prefixes in one place makes it simpler to keep track of them. But understood when it would be simpler to define a new prefix for a section of content.

3. “Couldn’t you have a simple tool that just shows you what prefixes are defined at any point in the document?” How such a tool has failed to exist in the XML world… may write this.

R is a high-level programming language used primarily for statistical computing and graphics. The goal of the R Programming Style Guide is to make our R code easier to read, share, and verify. The rules below were designed in collaboration with the entire R user community at Google.

If you are creating something for someone else, hopefully a paying client, there is a certain set of rules and protocols that you communicate with in terms of feedback, revisions, deadlines and deliverable. Some designers have created a custom process that they try and communicate with their client regarding expectations and some designers just shoot from the hip and hope things go smoothly.

Converts CSS rules into inline style attributes

LESS extends CSS with: variables, mixins, operations and nested rules.

Sass makes CSS fun again. Sass is CSS, plus nested rules, variables, mixins, and more, all in a concise, readable syntax.