For someone who complains about others' failure to address issues, you are redefining hypocrisy.
( . . . and, yes . . . I am unequivocally friggin' serious!)
You have again showed your ignorance and haste by implying that a solution must either be FULLY automated, or FULLY labor intensive. This, of course, is a fallacy. Naturally, we all know by now that CSGI is on the FULLY automated extreme <BIG gg>, and that IMRS may be on the other extreme. But ALYD is, to the remotely educated analyst, comfortably on the automated end of the range.
ALYD IS NOT A BODY SHOP - plain and simple.
How about having the brains, brawn or balance to address WHY their productivity was down . . . for that, not the raw employee numbers, is the real issue.
A: Code flow - plain and simple.
If your production facility is raring to go, capable of processing 360MM LOC/year, and code flow is not at an efficient level, then your "machine" is not running at optimal efficiency. However, as I addressed in a post to YOU weeks ago (with no response), to let these quality, TRAINED people go, only to need them back a month or two later (at higher wages) makes even less sense.
Any REAL arguments?
Remember, DO YOUR HOMEWORK, or stay away, BECAUSE I HAVE DONE MINE!
As always, the pleasure is mine . . .
thump9 |
