Thou shalt have no other gods before the ANSI C standard 1553

On Sat, 26 Feb 2005 02:35:33 GMT in alt.folklore.computers, Randy

That fact is recognized in the established professions, where you have to article, or the engineering equivalent: newbies get to do long hours learning the *basics* of their profession. It's only in computers that managers consider themselves qualified to decide that a newbie is sufficiently qualified to fill a team position, often without competent supervision, sometimes effectively trusting the company jewels to newbies.

rest march projects seem result when you have unqualified leaders and a bunch of newbies with lots of energy (for the first six to twelve months) who are initially thrilled to be involved in a real project delivering a product, until the first less than stellar feedback points out incorrect buttumptions made, leaders blame the newbies, and the newbies are expected to figure out how to fix the problems, without any real experience or knowledge of what they need to know.

I recognize participation in similar situations, and know people who worked on such projects at software companies, some of which failed when the project failed. It reminds me of livelock or page thrashing: those in charge fail to accept or recognize the situation for what it is, and don't know, can't come up with, or refuse to try, alternative approaches or techniques to get out of the situation and move the project over the bump, thinking that more effort will solve all problems, instead of applying effort intelligently.

The newbies need someone with more experience to point out when problems are likely to occur, to talk to when they realize they're in trouble, who will provide realistic advice, and ensure action gets taken to resolve issues to move things forward.

-- Thanks. Take care, Brian Inglis Calgary, Alberta, Canada

fake address use address above to reply