I totally agree. I perhaps should have clarified. It's not unmaintainable due to the code, its unmaintainable due to the lack of people capable of maintaining i

I totally agree. I perhaps should have clarified. It's not unmaintainable due to the code, its unmaintainable due to the lack of people capable of maintaining it. This is largely due to hiring me as the sole .NET developer (where their other devs who are primarily PHP devs felt somewhat comfortable with C#) and then deciding that I should be the sole Java developer instead (yeah, I was REAL happy about that), in case they ever want to put these apps on Linux machines or something else. Now, C# and Java are pretty close syntactically so hopefully they'll be OK. There is a huge difference in libraries and core API structure as well as deployment though, so it's not just an easy step to take. Having marginal .NET skills does not translate to marginal Java skills though. We do have a brand new Java dev, but it's really asking alot to put all of this on their shoulders with just a few months out of college.