44 lines
1.7 KiB
Plaintext
44 lines
1.7 KiB
Plaintext
From: trashcan at david-steuber.com (David Steuber)
|
|
Date: 26 Apr 1999 19:06:29 -0400
|
|
Subject: Designing Large Systems with Python
|
|
Message-ID: <m37lqz0yoa.fsf@solo.david-steuber.com>
|
|
Content-Length: 1424
|
|
X-UID: 482
|
|
|
|
Over my programming life, I have used a 'cowboy' programming style.
|
|
Once I have a general idea for a solution to a problem, I start
|
|
coding, using the text editor as sort of an etch-o-scetch. This works
|
|
fine for programs under about 10klocs (thousand lines of code), but it
|
|
is rather fragile and doesn't hold up to larger programs or the
|
|
requested additions of un-anticipated features.
|
|
|
|
I've noticed the acedemic and industry attempts to solve the problem.
|
|
OOA/OOD, UML, design patterns, et al are all proposed solutions.
|
|
|
|
Meanwhile, languages like Ansi Common Lisp have had features that
|
|
allow you to prototype and build a large system at the same time.
|
|
That is, the specification of the system becomes the system. People
|
|
have done the same thing with Visual Basic, so I am told.
|
|
|
|
What I am wondering about is the suitability of Python for specifying,
|
|
a large system and building a prototype. I have gotten myself rather
|
|
entrenched in the cowboy style and I would love it if Python supported
|
|
that for larger systems.
|
|
|
|
One other thing. Is the documentation that comes with Python
|
|
sufficient to gain mastery of the language, or should I consider
|
|
buying (yet) another book?
|
|
|
|
--
|
|
David Steuber
|
|
http://www.david-steuber.com
|
|
|
|
If you wish to reply by mail, _please_ replace 'trashcan' with 'david'
|
|
in the e-mail address. The trashcan account really is a trashcan.
|
|
|
|
A long memory is the most subversive idea in America.
|
|
|
|
|
|
|
|
|