On 16/08/07, Rajith Attapattu <[EMAIL PROTECTED]> wrote: > > > gets up to such tricks. There is also an out-of-date project, > > http://www.eecs.harvard.edu/~mdw/proj/old/jaguar/, that does this sort > of > > thing too, no idea but maybe the Terracotta folks got some ideas from > > there. > > > [RA] Sounds interesting. However my experience is that fancy solutions > often result in complex code hard to comprehend and difficult to maintain. > You heard about YAGNI? "suggests to programmers that they should not add > functionality until it is necessary" > We can adopt a strategy to keep the door open for all these > customizations, > but my experience most projects don't even end up doing these things. >
I'm definitely not suggesting that we do this stuff now, and it certainly sounds complex to do. But the best way to keep options open is through a carefully chosen interface. I think choosing the right interface is vital, because once it is chosen it is not likely to change.
