Quotes About Iteration

here's the genuine thoughtfulness and deep consideration for sake of truth and meaningful understanding. There's the recognition that if there were simple answers, we'd have already implemented simple solutions – and that not being the case, people have to work hard to discover the best - imperfect but with iteration ever-less flawed - courses of action and forget the pedantic and simple-minded debate points that so often mar discussions that should lead to progress.

That was the trouble with formulating a system: what could you do but repeat it?

Testing a product is a learning process

Design is all about learning from doing, that's how we evolve to the best solution.

Rule of Optimization: Prototype before polishing. Get it working before you optimize it.

I keep feeling I constantly debut every two years.

We struggle with the right words to describe the design process at Apple. But it is very much about designing and prototyping and making.

We've spent a lot of time on ergonomics. That was something we found to be really important as we iterated on the headset, from developer kits to Crescent Bay to the Rift.

Time makes a bigger difference: just making a game, shipping it, looking at what you did, how you did it, what you did well, what you didn't do well, and doing better.

It is a myth that we can get systems "right the first time." Instead, we should implement only today's stories, then refactor and expand the system to implement new stories tomorrow. This is the essence of iterative and incremental agility. Test-driven development, refactoring, and the clean code they produce make this work at the code level.

It is a myth that we can get systems "right the first time." Instead, we should implement only today's stories, then refactor and expand the system to implement new stories tomorrow. This is the essence of iterative and incremental agility.

Programmers can practice in a similar fashion using a game known as ping-pong.8 The two partners choose a kata, or a simple problem. One programmer writes a unit test, and then the other must make it pass. Then they reverse roles.

Dijkstra realized that these "good" uses of goto corresponded to simple selection and iteration control structures such as if/then/else and do/while. Modules that used only those kinds of control structures could be recursively subdivided into provable units.

If only we could pull this off one more time. If only we could just say we were done with implementation. But we can't, because the thing about implementation is that is actually has to be done. Analysis and design are not binary deliverables. They do not have unambiguous completion criteria. There's no real way to know that you are done with them. So we might as well be done on time.

To write clean code, you must first write dirty code and then clean it.

The most efficient and effective way to review code is to collaborate in writing it.

Analysis and design are not binary deliverables. They do not have unambiguous completion criteria. There's no real way to know that you are done with them.

We develop features before infrastructure and frequently show those features to stakeholders.

People never do something just once.

Fiddling with a program until it appears to work is a reliable way of obtaining a program that almost works

Dave West of Forrester Research came up with a term for this: "Water-Scrum-Fall."6) In other words, they've become the most efficient waterfall team that they can be.

With a tracer bullet approach, you can implement very small bits of functionality very quickly, and get immediate feedback on how well your team communicates and delivers.

If I'm doing a logo, I'll do it in black and white. Once the form is feeling right, only then do I start exploring the color palettes. A good example was the process of rebranding the Salvador Dali Museum. I did at least 100 versions in black and white.

We're on the brink of the next industrial revolution. Instead of buying things, you can make them on a printer. When you have a 3D printer, you can iterate more - what used to take months, now takes hours.