AW = RE in german :-) It's standart by outlook... > -----Ursprüngliche Nachricht----- > Von: Frank W. Zammetti [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 1. Juni 2005 21:55 > An: Martin Gainty > Cc: Struts Users Mailing List > Betreff: Re: [OT] Business Layer Ideas > > Leon, I meant to ask, what does the AW prefix on messages > signify? I've seen it plenty of times but never really > thought to ask until now. > > Oh yeah... IDE button-clickers... I HATE THEE! I have no > problem with a person that uses convenience tools so long as > they can do without them. I have no problem with using a > tool to generate getters and setters for a bean class, but if > you can't do it by hand then you have no business coding. I > actually know people that have no business coding, sorry as that is. > > -- > Frank W. Zammetti > Founder and Chief Software Architect > Omnytex Technologies > http://www.omnytex.com > > On Wed, June 1, 2005 3:43 pm, Martin Gainty said: > > There is always a cost As Leon pointed IDE button clickers are now > > called Software Engineers What happens when a requirement > comes along > > which is not acomodated by clicking 2 buttons? > > The entire project comes to an immediate HALT..the child prodigy > > sheepishly walks into his bosses office and cries he cannot do it > > since the IDE does not accomodate this feature..it is time > to call the > > 'dreaded consultant' > > The forgotten rule of Extensibility means that however you > build your > > app you must always be able to take on any features and > functionality > > that the client may desire Always best to Read/update and > understand > > the caveats of the requirements doc carefully before pushing *any* > > limited scoped solution into production.. > > Those who remember rolling your own customised solution > know this is a > > lost artform > > Martin- > > ----- Original Message ----- > > From: "Leon Rosenberg" <[EMAIL PROTECTED]> > > To: "'Struts Users Mailing List'" <user@struts.apache.org> > > Sent: Wednesday, June 01, 2005 2:44 PM > > Subject: AW: [OT] Business Layer Ideas > > > > > >>> > >>> One major problem lies with how programmers are educated today. A > >>> lot of schools teach a language or a design philosophy but rarely > >>> are in-depth enough to actually breed the abstract skills > necessary > >>> for the programmer to become useful. It's a shame, > really. I went to > >>> college in > >>> 1986 (and had been programming since 1978) and within a > few years of > >>> my graduation in 1990 the curriculum at most schools had been > >>> watered down to the point of near uselessness. > >>> > >> > >> Well, make a stop... You can't compare things programmed > back in the > >> Dark Ages with nowerdays programming. > >> We make far more complicated programms in far less time and for > >> lesser cost. > >> > >> You can critisize overusage of patterns, but under-usage > of patterns > >> is clearly at least as bad. > >> Patterns make code understanding simplier, because > everyone (should) > >> know them, and simplicity is the goal as many of us stated before. > >> You can't reinvent the wheel each time you write a piece of code, > >> it's simply waste of your time and customers/companies money. > >> > >> Regards > >> Leon > >> > >> > >> > >> > --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
