Re: Philosphy of programming
From: Programmer Dude (Chris_at_Sonnack.com)
Date: 02/17/04
- Next message: blmblm_at_myrealbox.com: "Re: Text Files In MSIE (was: Flame Bait! Windows vs: The Unices)"
- Previous message: Carl Gundel: "Re: Dijkstra gets it wrong [was: Re: D gets it right]"
- In reply to: Remo D.: "Philosphy of programming"
- Next in thread: Remo D.: "Re: Philosphy of programming"
- Reply: Remo D.: "Re: Philosphy of programming"
- Reply: Remo D.: "Re: Philosphy of programming"
- Reply: Remo D.: "Re: Philosphy of programming"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 17 Feb 2004 14:44:07 -0600
"Remo D." wrote:
> A pure top-down approach seems to imply a "perfect knowledge" in
> advance (I'll partition my reality in such a way that the
> different parts will only interact in predefined ways, however
> I will sub-partition them).
It doesn't have to. It can, in some cases, be grown as you explore
the problem. You start with the top "box"--"my program"--and then
divide that into the basic steps you know you need to accomplish.
Then divide those and so on.
The idea is that the approach is a tool for exploring the problem
space. If it becomes "ugly", perhaps your thinking is wrong (OR
this type of analysis isn't well suited to the problem).
> A pure bottom-up approach seems to imply a "reductionist" view (Let
> me prepare all this little pieces, I simply will need to assemble
> them at a later stage).
It's tedious making the little parts, but it's fun putting them
together and "suddenly" having a "working" program after all that
long development time. (-:
Top-down, OTOH, can provide you with a quickly "working" program,
although it'll probably be smoke and mirrors at that point.
> Maybe our (yet to discover) method for representing "models" should
> capitalize on this observation and directly suppot a way of working
> that proceeds by attempts: an initial model is created, it is
> checked against (representations of) real cases,...
You really should read Plauger's book. This is a big part of what
he's saying: use multiple tools/approaches to solve a problem.
-- |_ CJSonnack <Chris@Sonnack.com> _____________| How's my programming? | |_ http://www.Sonnack.com/ ___________________| Call: 1-800-DEV-NULL | |_____________________________________________|_______________________|
- Next message: blmblm_at_myrealbox.com: "Re: Text Files In MSIE (was: Flame Bait! Windows vs: The Unices)"
- Previous message: Carl Gundel: "Re: Dijkstra gets it wrong [was: Re: D gets it right]"
- In reply to: Remo D.: "Philosphy of programming"
- Next in thread: Remo D.: "Re: Philosphy of programming"
- Reply: Remo D.: "Re: Philosphy of programming"
- Reply: Remo D.: "Re: Philosphy of programming"
- Reply: Remo D.: "Re: Philosphy of programming"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|