So on my current project we primarily do packaging and deployment development. A-lot of InstallScript(Some for Windows MSIs, some for pure InstallShield installers), maybe some C# or VB.NET (or VB6 for the old systems).
We have a mostly new to the project team. One said member is what I call a 'Grey Knight(ess)'. That is someone who may have many years experience, is new to the project and makes demands as-if s/he was at the project genesis and/or had been around a while. I've only been programming for ~3-ish years, so I've never considered myself in a position to flat out refuse to work on a program/utility that is written in particular language. This individual is a sub(sub-sub-sub-maybe?) contractor so maybe her/his contract says s/he won't work on VB.NET/VB/Anything-resembling-BASIC. Also, s/he wants to get back into 'mobile development', something we do NONE of. Is the first WTF the interview process of the Prime/Tech Lead or the individual?
My issues being at-least 50% of the work we do is InstallScript(Worst of BASIC + Worst of C), 30% C#, 15% VB.NET(Or some BASIC derivitive), 5% Other. I am going to talk to my boss (and maybe boss +1 and boss + 2 which are easily accessible) on Monday. Any pro-tips on dealing with uh, developers that don't really fit the project?
I think there is work s/he could do, but the whole 'I haven't done BASIC since High-school and won't do it' mentality really rubs me the wrong way, considering said individual is some where north of 40. Seriously, you haven't dealt with a BASIC syntax language since, what, fucking 1980? Grow the fuck up.
Maybe I should have stayed with that VB6 project...