Read on Twitter
BUT WAIT, STEVEN you might say!
HOW LONG DO WE ITERATE??? SURELY WE DONT JUST GO FOREVER
Well, no. A good rule of thumb, in my opinion, is:
(
https://abs.twimg.com/emoji/v2/... draggable="false" alt="đ§”" title="Thread" aria-label="Emoji: Thread">!) https://twitter.com/Silent0siris/status/1320002483184410628">https://twitter.com/Silent0si...
HOW LONG DO WE ITERATE??? SURELY WE DONT JUST GO FOREVER
Well, no. A good rule of thumb, in my opinion, is:
(
* Core, experience-defining features: iterate as many times as you can, as long as you can. Stop when itâs ship time.
* Primary supporting features: 3 iterations after first implementation
* Secondary features: 2 iterations
* Tertiary features: implement, then iterate once.
* Primary supporting features: 3 iterations after first implementation
* Secondary features: 2 iterations
* Tertiary features: implement, then iterate once.
* Never: throw something in without time planned to make an iteration on it. By which I donât just mean balancing! I mean adjustments to the behaviors of the system, trying a new animation set, implementing a new resource meter, etc. Iterations probably take some code/anim/vfx.
