>Sheck their coding styles, commentinh, usage of OOP and anything else that
>fits your company's needs.
>
>Then make you decision based off that you see, not what you hear.

I remember an interview where I just sat with two Foxen and their boss (a VB/web guy, I guess) and talked for an hour about how would I do this or that, design patterns, known bugs in VFP (v7 then) and how do I avoid them, and I think from this the guys knew enough about my coding abilities; after about ten minutes we were rather exchanging ideas. I didn't really feel like I was questioned - it was more resembling a conference coffee break chat.

..and then there came the Question. Not that it was a trick question, but I sensed I may wake up on the wrong side of an in-house religious war. The question was to name three strongest points of VFP, and to name its three worst weakneses.

I had no problem answering that; the list emerged by itself. I only think, in retrospect, the last entry didn't merit to be mentioned. Whatever it was, it was there because I forgot the #1 downside of present day VFP... "it runs only on Windows".

To satisfy anyone's curiosity about the epilogue: I got the job but didn't take it.