That's sad to hear. I hope that you run into no more errors in c# to cuase you woes. But if that's the worst of what you get out of c#, and things become "better" for the company, then he made a wise decission. If things become crappy, then he made a poor decision. But none the less, approach him, ask him his reasonings for using c#, and why not languages like, java, c++, perl, ruby.. there must be key reasonings.