To be honest this sounds like a pretty typical gig. When you're rushing to get code together short cuts get made - paths get hard-coded, documentation doesn't g

To be honest this sounds like a pretty typical gig. When you're rushing to get code together short cuts get made - paths get hard-coded, documentation doesn't get written. Your gripes seem fairly minor. Not sure how something compiles in eclipse but not outside it (env variables, classpath, VM args?). And spending a day getting set up seems pretty rapid. 1) I don't think the business is going to crumble as a result of these issues. In fact it sounds quite the reverse, what with the investment and sales the business is making. If you quit they'll hire someone else who's maybe a bit more realistic about what real-world code bases look like. 2) You don't want to starting whining too early. Go with the flow, make incremental improvements as you go forward. 3) No. This will be a big job, and many things will have been doen the way they are for a reason. You risk annoying all your colleagues this way, and potentially creating more work when stuff breaks. 4) As I said above, this sounds pretty typical. Knuckle down. You are after all moving to a new language, it will take some time to get up to speed.