>>>>Can abyone see why this guy was let go?
>>>
>>>Was he the one who came up with the stp*sub* naming convention?
>>
>>in my book adhering to this convention makes refactoring via breaking out own subclasses much easier -
>>works great if you are up against a couple of 1000+ lines long functions from a previous dev who left the company...
>
>I agree about the advantage given by name sequencing when refactoring. For a work in progress, it looks pretty clever to me. The only downside is that, after the break-up, the sequence of steps has to be enforced by the programmer, whereas before, it was enforced by the program itself. As an example in the code sample, stp2sub40 is invoked before stp2sub10, which apparently breaks the sequence imposed by the naming convention.
>However, to be honest, the code looks pretty clear and maintainable. From the code samples alone, I see that he is (ab)using the logical expression evaluation in VFP, and he's assuming that all methods invoked there return a logical success value. Still, I don't see the clear reason for firing him (yes, the religious comments have no place there, but I don't find them offending since they refer only to himself. Would he had been fired if he stated that he got his energy from the glass of milk he had that morning? Those comments can be removed easily. If he put that in a messagebox, it would have been a different story:). Disclaimer: I am not a religious person. Neither do I drink milk in the morning, nor do I consider this the start of a conversation about religion.



I never said he was fired. This code was a nightmare to maintain because he wished to show others how much smarter he was than everyone else. A 40 function else condition is beyond the pale. Too bad we didn't have code-reviews back then, that would never have gotten traction. It was pure gibberish and gave no indication as to what was failing.

That code was written 2 years before he was let go, so he had multiple warnings and chances.