Okay, I really like that analogy. Not everything a carpenter can do requires an architect to draw up a blueprint though. For example, if I tell a carpenter I want a tree house with built-in seating and a window in the roof, no other requirements, can't they figure out how to do that on their own? So I then ask, what is a "good description"? Also, can't a model be well thought-out but not necessarily designed in a way compatible with the process of translation into code?

Thanks Lonnie.

On 6 Mar 2006 09:05:19 -0800, Lonnie Princehouse < [EMAIL PROTECTED]> wrote:
Object oriented languages lend themselves fairly well to this sort of
modeling, and a strong programmer in any language should be able to
take a good description of a well thought-out model and write some code
for it.

However, by far the harder part is designing a good model.  Asking
whether all programmers are capable of that is sort of like asking
whether all carpenters are architects.

As for Python, it's a good language for prototyping.  The development
cycle moves very fast, so one can experiment with many different ideas
more quickly than in Java or C++.  The price, however, is execution
speed. There are extension modules like the scipy suite which can
reclaim some lost speed, but Python will generally be slower than
compiled languages.

--
http://mail.python.org/mailman/listinfo/python-list

-- 
http://mail.python.org/mailman/listinfo/python-list

Reply via email to