Quotes About Iteration

In most projects, the first system built is barely usable. It may be too slow, too big, awkward to use, or all three." Cutler

Better to release the first version sooner with less. His was a less-now, more-later ethic. Robert

Moreover, multiplicity, iteration, and adaptation are universal concepts in that they are apparently important attributes for agents at all levels-from chemical reactants to biological ecosystems.

Incumbents are admittedly iterating on the friction, but have to butt up against compliance, legal and risk departments constantly trying to retain as much of the friction as possible. It takes a really strong CEO and executive team to reform that systemic thinking.

IDEATION ITERATION CODIFICATION EXPANSION Dream / Idea Experiment Convictions Welcoming Team? Learn? Disciples? Sending

One thing that being a scientist has taught me is that you can never be certain about anything. You never know the truth. You can only approach it and hope to get a bit nearer to it each time. You iterate towards the truth. You don't know it.

Nonetheless, you can start trying out generics and extended for loops today.

In software design, it's all about making a guess, trying it, and then learning from the experience.

Correction of the correction of the correction of the correction.

When it's hard to work on. I do it much quicker than most people do. I'll throw away code as soon I want to add something to it and I get the feeling that what I have to do to add it is too hard. I'll throw it away and start over and come up with a different partitioning that makes it easy to do whatever I wanted to do. I'm really quick on the trigger for throwing stuff out.

XP always keeps the system in deployable condition. Problems are not allowed to accumulate.

To maximize your chances of success, you should deploy small, concrete experiments that return concrete feedback.

We're going way too slowly, with too much wip and too many features in flight. We need to make our releases smaller and shorter and deliver cash back faster, so we can beat the internal hurdle rate.

Instead, code is only "done" when it has been fully tested and is operating in production as designed. (Note

Continuous Delivery.

do we work in small batches, ideally single-piece flow, getting fast and continual feedback on our work?

Instead of project teams where developers are reassigned and shuffled around after each release, never receiving feedback on their work, we keep teams intact so they can keep iterating and improving, using those leanings to better achieve their goals.

Small batch sizes result in less WIP, faster lead times, faster detection of errors, and less rework.

It takes sometimes years in the market to get the tuning to the right place where your game is as compelling at level 100 as it was at level 10.

Everything that happens once can never happen again. But everything that happens twice will surely happen a third time.

repeated serial exposure.

We need to send duplicate ghosts out to each possible router endpoint, wait for an echo, then iterate and repeat. Recursive depth-first traversal.

You don't have to make every module perfect before you check it in. You simply have to make it a little bit better than when you checked it out.

One revolution is like one cocktail, it just gets you organized for the next.