|
|
|
|
|
by skrebbel
3553 days ago
|
|
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 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? Come on. They're an enterprise like any other and they use what the OP calls "enterprise-level type checking and refactoring capabilities". I agree that it's a stupid name but I think you're misunderstanding on purpose. |
|
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.