prototyping good OOdesign in Python?

[Roman Suzi]

On Sat, 1 Jun 2002, Ken Seehof wrote:

>> prototype certain design? Developing in C++ looks so unnecessary hard
>> after things were done in Python...
>> Or, it may be put this way: what discipline a Python programmer must
>> obey to allow it's prototype to be conveniently rewriten in C++?
>> The above thoughts aren't probably well-formed. But I hope
>> my concern is understood.
>>
>>
>> Sincerely yours, Roman Suzi
>
>I agree with what you are saying.  Here's my approach :-)
>
>0. Write a project schedule for management; something like this:
>   1. Prototype in python
>   2. Convert to C++
>1. Prototype in python
>2. Give a nice demo, and convince management to skip step 2
>3. Re-implement a few cpu intensive classes in C++

Interesting ;-)

>Since most of the code never /actually/ gets rewritten in C++,
>the need for special C++ "discipline" in the python code goes
>away.  Weeks are slashed from the schedule, and the program is
>more maintainable.
>
>Another nice advantage is that the python programmer gets to ask
>for a raise, and has excellent job security!

...because only he knows the magic powers of Python?

>There may be a few oddball examples of projects that actually
>need to end up written in C++ after prototyping in python, but
>for the most part, the most common reason to target C++ is to
>alleviate fear of the unknown.  (Hmm, is this also why people,
>(including myself), still buy from Microsoft? :-)

Fear of unknown? That is why I DO NOT buy from Microsoft ;-)

>- Ken Seehof

Sincerely yours, Roman Suzi
-- 
\_ Russia \_ Karelia \_ Petrozavodsk \_ rnd at onego.ru \_
\_ Monday, June 03, 2002 \_ Powered by Linux RedHat 7.2 \_
\_ "Bugs are Sons of Glitches!" \_