I usually let things repeat themselfs until I feel it's more trouble then it's worth. This way I can refactor patterns / components / models / whatever when I actually *know* I need them repeatedly and not if I just *think* I might. Trying to have everything at a maximum re-usability level is a battle that is hard to win. So I usually look over the battle-fields of previous projects and decide what soldiers did well and then clone them into über-killer-machines ; ).
Trying to build a library first for all the stuff one might needs can be a fun exercise, but it usually takes a long time and most stuff won't be needed or not needed in the way one imagined. That's my take on the topic ; ), -- Felix -------------------------- My Blog: http://www.thinkingphp.org My Business: http://www.fg-webdesign.de Max wrote: > Hey guys !! > > I've been thinking from a last few days, that how many hours can I > save if I build a library of all my reusable code/modules which is > very easily accessible while working on a project... ? Dont you think > that will save time ? > Some of you might be already doing it ? > > The problem right now I'm facing is, I dont keep track of every > reusable snippet and while development on the project, I have to find > important code from old projects etc.. Is it just me or it happens to > all of you ? > > Is there some special type of library which can be built on a local > machine or server which will help us implement the pre-developed code > easily ? Please share your ideas and do post your methods which you > use to handle it... > > Thanks > Max > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
