Re:Choose Boring Technology (2015)
by cbm-vic-20 on Sunday February 21, 2021 @10:34AM
(#26214159)
The GP comment mentions the need for finding engineers with "a proven track record of delivering value", yet here we have a concern about "hiring random Java developers".
Is the industry biased against great engineers who have been working with Java for the past 20 years, even if they "deliver value" (which is pretty much impossible to determine externally)?
Re:Choose Boring Technology (2015)
by lostcolony on Sunday February 21, 2021 @02:07PM
(#26216151)
No.
But I, personally, am biased against hiring people with only Java on their resume. Because 90% of the time what I've encountered are people who haven't examined their technology choices, questioned the status quo, tried to -improve- things.
That's not a sleight on Java, per se, but it is against anyone with only one language on their resume. It's just that if there is only one language on a resume in web dev land, it's almost always Java.
Re:Choose Boring Technology (2015)
by blandflakes on Sunday February 21, 2021 @11:57AM
(#26215013)
Yup - it's possible to build uncomplicated software in Java, especially in recent iterations of Java and more... restrained modern frameworks. However, there's no guarantee that you're actually going to either join a team or hire a Java expert with those tastes.
Re:Choose Boring Technology (2015)
by whimsicalism on Sunday February 21, 2021 @10:31AM
(#26214150)
> everyone who learned Java in school and never felt like looking at another language
A large reason I avoid Java teams.
Although still new I'm wondering whether Kotlin could be admitted to the boring technology category given that it was built to dovetail with Java and has first class Spring support?
I’ve found kotlin to be wonderfully boring. There are definitely some sharp knives that get abused though. I’ve met a few people who want to throw OO in the bin and treat kotlin as pure FP to their detriment.
Isn't that a real option with Arrow?
Java is definitely "boring technology", but hiring random Java developers will probably sink a company faster than doing the same for Go.