Part of having the right people is letting them make high level design decisions. This would have a major impact if there are multiple projects in process. So much like a large company that might share an accounting dept across divisions, you can share code across divisions.

There appears to be a difference in philosophy between dotnet/java camps. There are several options for purchasing the plumbing necessary to start a dotnet app, codesmith for the data and the various frameworks, for example.

There seems to be a hesitation to buy anything in the java camp. What's discussed a framework in Java, isn't the same thing as dotnet. Spring is a framework in java. It is much more generic. The main purpose is to allow for more dynamic code. You provide parameters in XML that define what code modules to load.



>Perry,
>
>no discussion on the merit of having qualified people. But arguing to have the right people to write the basic layers sounds wrong: why create [this much] for yourself ? Even in relatively small markets like vfp you can get a boost by frameworks very cheap compared to the value added. For large project this -in the best cases - translates into making some packages work together, sometimes into recreating a pentagon and an octagon and praising it as the best wheel-combination ever<g> - but IMHO on java projects too much is spent on infrastructure, even considering balloning cost found in large projects. Anything similar happening at your side ?
>
>curious
>
>thomas