|Jan 7, 2011, 06:56 PM||#2|
Reminds me of the old classic "Problem Solving Flowchart" http://dangerousintersection.org/200...ng-flow-chart/
MBA (13" 1.7 GHz 128GB), UMBP (15" SD 2.8 GHz), UMB (13" 2.4 GHz), iMac (17" Yonah), 32GB iPad 3 WiFi+LTE, 64 GB iPad WiFi, 32 GB iPhone 5, Airport Extreme
|Jan 8, 2011, 10:41 AM||#5|
What's missing is statefulness.
If you code well after coding fast, and learn from your prototypes, you might be able to finish before obsolescence.
It's called "Throw the first one out".
... maybe the first several. A programmer will make mistakes. You can't fix stuff until you make the mistakes, so you might as well make mistakes (in the general direction of the spec) as fast as possible. What you might learn from the hacked up early versions is how wrong the specs are when you actually play with the app, and what parts you might need to code well to finish.
Then rewrite (and rinse and repeat).
|Thread Tools||Search this Thread|
|thread||Thread Starter||Forum||Replies||Last Post|
|Write The Code. Change The World. Is it Objective-C 3.0 ?||hassoon||iPhone/iPad Programming||37||Jun 10, 2014 03:51 AM|
|Write the code change the world||Jb2k||OS X||2||May 29, 2014 07:40 AM|
|Write Code that Updates Itself?||ArtOfWarfare||Mac Programming||2||Jun 2, 2013 06:31 PM|
|Can we write assembly code iOS based devcies?||Narendar Singh||iPhone/iPad Programming||4||Aug 6, 2012 06:19 AM|
|what program easier to write serialize QR Code?||Ashley355||Mac Applications and Mac App Store||0||Jun 4, 2012 07:59 AM|
All times are GMT -5. The time now is 08:18 AM.