Email dredging: Cutting polish and nonlinear results

Tynan Sylvester · 18 Dec 2013 · tynansylvester.com ↗

5 korrents from this piece

Tynan Sylvester did not write this page.

Every claim below was made in this piece, quoted word for word and numbered in the order the piece makes them, so you can read it there rather than take our word for it. The sentence above each quote is our reading of the claim, not their wording. Each quote was checked against a stored copy of the page at build time; where the two differ, the quote is the fact.

Our reading
In game development speed is quality, because the faster you can work the more times you can iterate.

Their wordsIt’s my strong belief that in games dev, speed is quality.

Interesting
Our reading
Quantity produces quality: the more work you put out, the likelier it is that one piece of it turns out to be the one that matters.

Their wordsSpeed is quantity, and quantity is quality – The more stuff you put out, the more the likelihood that one part of it will turn out to be really, really important and good.

Interesting
Our reading
What a finished work is remembered for comes down to a few key pieces, and most of the work that went into it barely matters.

Their wordsthe final experience often comes down to just a few key pieces or insights.

Interesting
Our reading
The way to find a hit is to experiment a lot, not to polish.

Their wordsI don’t think the answer is “polish”. It think it’s “experiment”.

Interesting
Our reading
A small studio’s advantage over a large one is the ability to change direction fast, not the ability to out-polish it.

Their wordsOur advantage is agility and lack of corporate cultural encumbrance.

Interesting