It tends to be "process oriented" and not "creativity oriented"--which may be why India's so in love with it. That, and it gives management thw warm fuzzies to hear it.
(Tends to work best for large, hidebound bureaucracies that have the turning radius of an aircraft carrier, rather than startups and other nimble organizations...)
Cheers!
All that matters is that they are hugely profitable. Thats all the smarts needed, IMHO.
Agreed. Show my cyclomatic complexities by function. Halstead volumes are helpful too. For object-oriented software, fan-in/fan-out per class. Instrument the code and run a coverage analyzer to expose just how much code is actually being run. Execute with a memory checker e.g. BoundsChecker or Purify to expose sloppy handling of memory. Run a good quality Lint e.g. Flexilint over C code to look for abysmal coding screwups. Get a ratio of lines of code vs comments. See if the comments are actually correct. Use a code profiler to examine call paths. A good analysis tool can spot calling hierarchies. An excellent one doesn't fall apart when indirect recursion magically shows up.