A company I worked for had an internal project that was a .NET monstrosity (the rest of the firm was either mainframe/COBOL or JVM based). They named it "Proje

A company I worked for had an internal project that was a .NET monstrosity (the rest of the firm was either mainframe/COBOL or JVM based). They named it "Project Maelstrom". A more apt name could not have been had. Note: .NET is not bad in itself, I guess, but we had no real production experience with it and was mostly spearheaded by people who used it as an REU (Resume Extension Unit) to get jobs at Microsoft, with little to no actual justification for using it where we did. I guess that was their dream, and for at least one person it worked as such. But I always felt it was kind of underhanded.