[Home] [Groups] - Message: [Prev in Group] [Next in Group]

nu.kanga.list.mud-dev

28356: Re: [MUD-Dev] Architecture (Cell Rebalancing)

[Full Header] [Plain Text]
From: "Peter \"Pietro\" Rossmann" <peter.rossmann@telia.com>
Newsgroups: nu.kanga.list.mud-dev
Date: Thu, 3 Jul 2003 10:15:55 +0200
References: [1] [2] <-newest
Organization: Kanga.Nu
"J C Lawrence" <claw@kanga.nu> wrote:

> Hit the list archives.  Its all there.  You might also like to dig
> back

i know there are some pearls in the archives, but without the search
function working, it's a though job,i am reading articles based on
subject - which means i'll miss many of them. ("An error occured!
could not connect to server: Connection refused Is the server
running on host localhost and accepting TCP/IP connections on port
5432?" )

> Start out by stating what you want to do.  Clearly, simply, in no
> more than a half dozen nice declarative sentences.  Beat on that
> for a while

this is exactly what am i doing now.

>> The trouble with many architects is that they start to program
>> too soon, in too detailed areas and the result is no good then.

> Yup.  The same is true of many architects: they design far too
> soon and in too much abstraction.  Design is a Good Thing, but can
> kill a project just as readily as lack of design.

i don't have a project to kill :) i just got deramy about design of
NGPW (Next Generation Persistent World :)))

too much abstraction is problem only at the start of implementation,
until then, the architect can still work more on it. But i agree -
too much abstraction at the enddesign leaves too many options to
implementators. if all the possible options are equivalent, that's
not a problem. but they usualy aren't.

Pietro
_______________________________________________
MUD-Dev mailing list
MUD-Dev@kanga.nu
https://www.kanga.nu/lists/listinfo/mud-dev