Global in multiple files

Roman Suzi rnd at onego.ru
Mon Jun 11 09:39:51 EDT 2001


On Mon, 11 Jun 2001, Alex Martelli wrote:

>"Roman Suzi" <rnd at onego.ru> wrote in message
>news:mailman.992228330.22368.python-list at python.org...
>    ...
>> >Mhm. It seems a little too much overhed for a simple list of users.
>>
>> What if one day you decide to use threads and userlist is to be shared.
>> How do you manage your list without breaking it then? But if some object
>> will be in charge of this resource, it will be much-much easier. You will
>> need blocking written only once.
>
>There is a serious risk in over-designing systems "because
>one day it might be handy".  Yeah, right, but meanwhile you're
>paying the price of complexity *RIGHT NOW*!-)

I always try to choose more flexible way as long as
it doesn't add to complexity. When it is style of
thinking, it doesn't require much overhead to always
code more generally than is required "right now".
I have too much work "right now" to mend things
which were somebody's "right yesterday".

Somehow, more general solutions do not always require
more work or mean more complexity, but are of better
quality.

>"Do the simplest thing that could possibly work", because
>"you ain't gonna need it" (where "it" is the rich, complex,
>over-engineered, over-designed very general solution:-).

That is why Microsoft systems still have those funny
A:, B:, C: letters before file paths ;-)
Because "right yesterday" 640K was enough for everything.

>See http://c2.com/cgi/wiki?YouArentGonnaNeedIt ...
>
>
>Alex

Sincerely yours, Roman Suzi
-- 
_/ Russia _/ Karelia _/ Petrozavodsk _/ rnd at onego.ru _/
_/ Monday, June 11, 2001 _/ Powered by Linux RedHat 6.2 _/
_/ "Useless Invention: Fur sink." _/





More information about the Python-list mailing list