Thanks for the passionate response, its good to read something written from the heart. However I would like to address a few of your points.

Is their some aspect of life that is without passion? Look - it's all about why some guys are content playing in a club band and others want people to buy their CDs and have sex to their music. And I am practicing a motivational style. At the end of this thread I will ask you to send me money.

Some want to be liked - and some want to be loved!

How many marquee geeks are part of a team? I never see Marcia and Company - or Fournier and Company or Strahl and Company or Holtzer and Company.

You never see Sergey and Company or Rodman and Company.

When we log into the UT we log into greatness!(c)Terry Thurber 2006

Everybody here is a cocky bad a_s engineer. Everybody here.

Big teams consist of the inner circle - the double secret librarians and guardians of the triple secret class libraries. They know one thing: The boss might be hesitant to fire the secret order of class library guardians. The outer cloister knows one thing - if the inner circle keeps their job - then the outer ones will most likely keep their jobs (too).

It's hard holding your head up when you realize that 90% of the reason you were hired is that you could pass a urine test! (I had to say it - why - why do I talk like this?)

Class librairies are a ruse. They are a substiture for good coding procedures. Any project could be simplified with just good coding practices.

Can I recompile our FPW program into dot NOT?

Any project can be built just shluffing the classes off the IDE bar! Development is a lot simpler than team construct advocates let on - maybe they just don't know?

The problem with the "Team" is that conserves and complicates. Quality will "sink" to the lowest common denominator. Customer disatisfaction will always be expressed in terms of the limitations of the tool rather than what it really is - just a lazy sexless design.

I can't wait to see my first FPW recompile in Sedna!

This could be argued for any language surely, one java developer could write any java app, one .NET developer could write and .NET app, etc.

Language or tool is secondary. If we work with node collection objects a lot - like treeviews, xml, listviews, winsock, cdo (drive Access using it's ODBC COM rather than the desktop GUI) we can work in any environment or language.

The heart of a solution is not the syntax that defines the background color for a label - the heart of the solution usually involves manipulating those specialized node collections that any platform can instanciate.

Syntax structure is pretty much the same for all programming languages. And I have found that full cycle developers - since back in the daze - have the same approach to structuring a solution. It's almost like it is the same guy.

But when you think about it - there is a universiality (wow!) to structured top down methodologies (you kids just never got to write big detailed flow charts)! You kids never had your wrists slapped for a sloppy design or laughed at for guessing!

You kids never had a bet to see who could solve the same problem with the fewest punch cards! Dag Nag It!

How then would that same single developer keep up with the simultaneous requirements of several clients, would they be placed in a queue and be dealt with one at a time?
Hire a contractor.

That might work in some cases but the only way to do more than one thing at a time is to have more than one person do it.

And this is the "thing" grasshopper - where we should see oppertunities to exercise our gifts - we see frustration, misgivings and doubt.

Fear of failure. There is a way around. It does not matter if you consider your self smart or stupid. Look in the mirror and tell yourself you're smart. Here's the way it works: Either you are endowed enough to assure sucess - or you are too stupid to realized you can't "cut" it - and will hack it out till you get the result - or die trying - or go work at Circut City. (of course - you could become Team Manager - and just ride on the backs of your the brighter more agressive engineers on the bench.

Rule: No one is stupid - some people are just wussies. Don't be a wussie. Wussies usually endup being MicroSoft Repairmen!

In addition to that as you are posting on the Universal Thread I assume you recognise the benefit of other people's ideas.
If it was not for the thread - I would be recomiling FPW programs in Sedna. Like I said, when we log into the UT, we log into greatness.

Where else can we get we get scolded by Marcia - harassed for grammer by David - or have the context of a thread generalized by Bernsten? Where else would a David F pamperer us through some arcane class or API?


Where else?