• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Design for Cocoa (was Re: Can a subclass of NSDictionary do this?)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Design for Cocoa (was Re: Can a subclass of NSDictionary do this?)


  • Subject: Re: Design for Cocoa (was Re: Can a subclass of NSDictionary do this?)
  • From: Georg Tuparev <email@hidden>
  • Date: Thu, 24 Jul 2003 11:43:05 +0200

On Thursday, Jul 24, 2003, at 05:59 Europe/Amsterdam, Tim Ramsey wrote:

Suppose I am building a complex mathematical/logical algorithm (one of the things I do). Detailed design is very important here because poor planning and/or bad data structure choices can make life a nightmare and may make the job impossible. You can paint yourself into a corner where you find yourself building and rebuilding endless code and getting nowhere. Flow charts and data structure diagrams are great in this situation, and if they look like an explosion in a spaghetti factory, start over. A great design will achieve a certain inevitable simplicity, even for a complex problem. It will also run much faster than a poor design. I have constructed optimized designs for kludged up systems that reduced runtimes by factors of over 200 in extreme cases.

Well, here a real example. Many years ago, I was doing computer aid protein folding. Horrible force fields, no papers/text books where to look for ideas, chemistry, fuzzy biology, NMR spectra - all ugliness at once. We wanted to as questions like: "What if we mutate this amino acid", or "Where should we put a sulfur bridge in order to make the enzyme termostabile".

We went to a greek restaurant, and when the ozo was served, we start brainstorming. We end up with a "soup" metaphor (our architecture so to say), and next day we start wildly coding with not a single line of design! Several years later, we end up with what is now one of the standard software packages, and 2.7M lines of very well structured, maintained, and extremely readable software.

Rafactoring, Test-First-Development, and Pair Programing were the keys to success. At the end we had about 15 pages of design document written for newcomers...

BTW, this story started 15 years ago...

have fun

Georg Tuparev
Tuparev Technologies
Klipper 13
1186 VR Amstelveen
The Netherlands
Mobile: +31-6-55798196
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Design for Cocoa (was Re: Can a subclass of NSDictionary do this?)
      • From: Tim Ramsey <email@hidden>
References: 
 >Re: Design for Cocoa (was Re: Can a subclass of NSDictionary do this?) (From: Tim Ramsey <email@hidden>)

  • Prev by Date: Network interface
  • Next by Date: ASCII to hexa
  • Previous by thread: Re: Design for Cocoa (was Re: Can a subclass of NSDictionary do this?)
  • Next by thread: Re: Design for Cocoa (was Re: Can a subclass of NSDictionary do this?)
  • Index(es):
    • Date
    • Thread