It Compiled. It Ran. Nothing Got Written. Diagnosing a CA 2E-generated program that returns clean, throws nothing, and still doesn't do the thing — and why calling it directly is not the same test as running it for real A compile error is, in a strange way, the easy case. The compiler stops you, points at a line, and you fix it before anyone downstream ever sees the problem. What actually costs people time on CA 2E work isn't the 1,600-message compile listing — it's the progr...