Iterate Twice, Code Once
Planning ahead saves time
Issue: 7.2 (January/February 2009)
Article Description: No description available.
Article Length (in bytes): 3,694
Starting Page Number: 48
RBD Number: 7214
Resource File(s): None
Related Link(s): None
Known Limitations: None
Excerpt of article text...
Thankfully, my old 8th grade shop teacher recommended a math and science track for me rather than woodworking. Due to my less-than-stellar shop performance I have a permanent order of protection against woodworking tools. That teacher should be proud though, because I'm going to talk about the old-adage of measuring twice and cutting once.
I can hear your thoughts: Bob, why the heck are you talking woodworking when you're a software developer? That's a great question and one that will make sense when we're all done.
I recently attended an iPhone Tech Talk conference and was impressed by the amount of time they spent talking about the design aspect of making a good iPhone app. They kept pushing that design doesn't happen just at the beginning, but that it's an iterative process throughout the project. Great iPhone apps don't just appear, they evolve.
The iPhone Tech Talks definitely hammered the design process home. They gave concrete examples of how successful iPhone apps started out on paper as sketches before any code was written. They iterated their paper design many times to get the look and feel they wanted before writing any code. There are a couple of reasons for this process, of course.
...End of Excerpt. Please purchase the magazine to read the full article.
Article copyrighted by REALbasic Developer magazine. All rights reserved.