View Single Post
Old 01-31-2008, 07:11 PM   #14
Turby
Newbie
 
Join Date: Mar 2006
Posts: 33
@ mnwcsult...

I'm with you 110%...

I've been in the industry over 20 years and have to agree with you 100%, the only reason we have use C# / .NET is because of a client requirement. The amount of "bloat", sluggish performance, massive hardware resources and general instability is a constant source of concern - it doesn't help when the Visual Studio 2005 .NET IDE regularly flakes away on the developers and testers.

Embedded systems use ANSI C, ASM, Delphi 7, Pascal - all depends on target platform and available tool sets to meet safety requirements.

The actual writing of code amounts to no more than 20% of the effort, the rest goes in requirements, design, test, documentation and maintenace - all of which is rarely taught these days in college as basic software engineering principles. The documentation we get provided by some "out-sourcers" is basically reversed engineered from the code using tools such as DOxygen - reams of fancy looking stuff that looks good but is more or less useless for maintenance purposes or even understanding the basic software architecture.

The likes of VB and Java has its place for short term / throw away software that has a minimal lifespan - ie college coursework, GUI prototypes and small home projects.
Turby is offline   Reply With Quote