• 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, Architecture, and Thought Processes (Was Re: shopping carts)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Design, Architecture, and Thought Processes (Was Re: shopping carts)


  • Subject: Re: Design, Architecture, and Thought Processes (Was Re: shopping carts)
  • From: Chris Hanson <email@hidden>
  • Date: Wed, 27 Aug 2003 17:39:38 -0500

On Tuesday, August 26, 2003, at 12:57 PM, Chuck Hill wrote:
The last problem that comes to mind is the desire to know absolutely every detail of the implementation of the code being used, rather than relying on the abstractions it provides.

A related problem that I see a lot is a belief that everything can be known and designed for up-front. Many developers have been told that the opposite of code & fix development is doing a big design up front, so they strive to know everything they possibly can up-front and create a huge plan for even the smallest project.


Now, that *is* a better strategy for actually delivering software than code & fix development. It's much more likely to result in delivering software on time and on budget that satisfies the client. However, that's only relative to code & fix -- big design up front (aka "waterfall") still has a terrible track record for delivering.

  http://c2.com/cgi/wiki?BigDesignUpFront

Iterative and highly adaptive agile methodologies like eXtreme Programming are much better at (a) delivering real client value in a short timeframe and (b) preventing the kind of analysis paralysis described above. When you're focused on shipping a small release with a small feature set in two weeks, and incrementally improving it, you simply don't have time to do anything but the simplest thing that could possibly work.

  http://c2.com/cgi/wiki?ExtremeProgramming

One of the things I find really interesting is that a lot of people practicing agile methodologies are in the J2EE/Swing and .NET worlds. I think WebObjects and Cocoa both actually get you a *lot* more bang for your buck with agile methodologies -- you can do a lot more points' worth of user stories in the same amount of time using either WebObjects or Cocoa than you can with J2EE/Swing or .NET.

If anyone is doing Cocoa-Java development and wants some help setting up JUnit to run automated unit tests from Project Builder, let me know off-list. I've done it and it works reasonably well, almost as well as OCUnit (modulo the fact that you have to manually add test suites to a master suite that gets run, which is a JUnit issue rather than a Cocoa-integration issue).

  -- Chris

--
Chris Hanson, bDistributed.com, Inc.  |  Email: email@hidden
Custom Mac OS X Development           |  Phone: +1-847-372-3955
http://bdistributed.com/              |  Fax:   +1-847-589-3738
http://bdistributed.com/Articles/     |  Personal Email: email@hidden
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Design, Architecture, and Thought Processes (Was Re: shopping carts) (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: Design, Architecture, and Thought Processes (Was Re: shopping carts)
  • Next by Date: RE: Can Webobjects Do This..
  • Previous by thread: Re: Design, Architecture, and Thought Processes (Was Re: shopping carts)
  • Next by thread: the height is still not working...
  • Index(es):
    • Date
    • Thread