Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS xkcd Cartoon: How To Write Good Code
- Thread starter dejo
- Start date
- Sort by reaction score
Reminds me of the old classic "Problem Solving Flowchart" http://dangerousintersection.org/2008/05/17/problem-solving-flow-chart/
B
B
And it happens to me every day...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).
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).