Very good points, Mr. Carroll. Taking your analogy to heart; The problem I always seem to have in crafting swords is this: I go out and find expert-designed swords that I could use. However, the expert swords seem to be very generic and often contain bells and whistles that seem like dead weight to me. I find that I could make my own sword much sharper and faster for its own specialized tasks than the generic expert-designed sword by hardcoding my own specialized sword. Is this bad practice? Should I always opt to rely on generic 'expert' code and take on its dead weight rather than building specialized code? I'm sure there are many implications and trade offs...
________________________________ From: Charles Carroll [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 12, 2005 8:46 PM To: [email protected] Subject: Re: [AspNetAnyQuestionIsOk] How to split the UI for each of the Page. There are 300 ways to become good programmer --- writing something some one else already wrote is not one of them. Since all these controsl come with source reading the source and attempting to understand it will make you a great programmer just like studying a sword made by a great craftsman will teach you how to make good swords. Learning guts is done by seeing how skilled craftsman who know the guts make it work and improving or extending that work. 90% of the ;lousty work I have seen is by people that use the guts incorrectly because they have never looked at any other expert's code. Good design is hard, it takes at least 3 drafts or more to get object designs right. You may take their object and make a replacement that is better or you may learn if their work is superb how to craft better objects yourself. In the modern world we don't build and design our cars from scratch, even if we want to design and build our own cars we study designs before ours, drive the vehicles, study their design and parts and then craft the venhicle we want orout of many different pieces of each car and maybe invent some new pieces to connect or replace existing ones. Anyone designing code and objects and APIs without surveying what other great minds did on the subject is like someone who has not read the great writers or any writers attemprting to write, or someone who has never looked at other paiter's works trying to paint. On 4/12/05, Mat�as Ni�o ListMail <[EMAIL PROTECTED]> wrote: > > Good points, if your aim is to save time. My aim, however, is to learn > ASP.NET <http://ASP.NET> and to become as familiar as possible with its > guts. Why should I spend time learning some 3rd party's API when I can spend > the time learning how it all really happens? Doesn't the latter make me a > more learned programmer in the end? > [Non-text portions of this message have been removed] ________________________________ Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/ * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service <http://docs.yahoo.com/info/terms/> . [Non-text portions of this message have been removed] Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
