[coldtea]

>* Oh come on, you're not even trying. He means, the type checking and refactoring capabilities that you want to have in a large team that relatively quickly changes composition. I.e. the kinds of teams you often find in enterprises.*

I rarely find such large teams in enterprises.

What I usually find is ad-hoc projects, some in VB6, some targeting IE6 in 2016 still, others in J2EE with "enterprise" application servers, etc. Most done by 1 to half a dozen people. And I don't see them "quickly changing composition" -- the same persons work in the same IT deps for decades...

>I doubt Google doesn't use any of the type checking and refactoring tools that come with all Java IDEs out there. You think they rename Java methods with command-line search&replace just to stay in touch with their inner startup?

No, I mean there's nothing enterprisey about refactoring.

[jimmcslim]

> the same persons work in the same IT deps for decades...

Guess I've found my solution to my persistent angst over the repeated 'old geeks are screwed' stories around here!

[coldtea]

Well, of course. Old geeks are screwed on startups and startup-y companies.

The enterprise IT (and the financial sector, major organizations, etc) are the places where old geeks are quite ok -- if not to hire, surely to keep past 40 and 50 when they have already been working for you. The median age in an IT department in a large enterprise is much higher than in any SV startup.