4 ms·
> But are language enthusiasts really better hires in general? I've known many of them who loved the theory and toying with a language but were not any better a
by kqr 9y ago
> But are language enthusiasts really better hires in general? I've known many of them who loved the theory and toying with a language but were not any better at producing actual value than the average joe.
I think they may be safer hires, anyway. They will be able to program themselves out of a wet cardboard box, which is more than you can say about the average Joe who may just be good at bluffing the interview.
- crdoconnor 9y agoProvided you dangle enough money and have a good interview process you can easily cull those people who can't code themselves out of a wet paper bag. The thing that would worry me about niche languages is the amount of wheel reinvention you'd have to do. Not sure the cost/benefit calculation starts to look so great any more when you realize that your enthused elm developers will have to build a whole lot of stuff that you can just import in other languages.
- jimbokun 9y agoNot sure how Elm interacts with Javascript libraries, but JVM languages can generally use any existing Java libraries. So a language built on a popular run time (JVM, .Net VM, guess there's exactly two), can still have excellent library support.
- krotton 9y ago...or Node.js nowadays, so three, I guess. Elm nicely abstracts over JS interoperability with a mechanism called ports: https://guide.elm-lang.org/interop/javascript.html https://guide.elm-lang.org/interop/javascript.html
- rebeccaskinner 9y agoMost niche languages have an FFI escape hatch for when you really need a library and don't want to re-invent a wheel. Elm, Purescript, Bucklescript, and ghcjs can all interoperate with javascript; Scala and Clojure work with most (all?) native java libraries; F# has access to most (all?) .NET libraries. Haskell, Idris, ATS, Erlang, and SBCL Common Lisp all allow you to access native system libraries. FFIs can have warts, but in the general case library support isn't the obstacle people make it out to be.
- crdoconnor 9y agoI don't agree. I find that the impedance mismatch of an FFI is an incredibly fertile breeding ground for nasty and obscure bugs and deployment problems.
- dragonwriter 9y ago> Provided you dangle enough money and have a good interview process you can easily cull those people who can't code themselves out of a wet paper bag Interviewing costs money—good tech interviewing particularly so. The less of the people you have applying to start with, the more money you save on culling then by way of tech interviews.
- droidist2 9y agoTrue, I'd much rather someone who spends their time learning Elm than Cracking The Code Interview.
- Can_Not 9y agoAren't you just as likely to get people who excel at hyping and hello-worlding new languages but can't actually make applications? Or people who just read the python paradox (with python scribbled out and Elm written over it) who think they can look like a great developer who understands the value of Elm but really don't?
- kqr 9y agoYou'll get those, yes. I know because I was one of them... But I think you unerestimate how bad the average interviewee can be. Someone who hello worlds new languages may not know the syntax or idioms to write fizzbuzz in any specific language, but they will be able to characterise the rough shape of the problem, and not just sit in silence...
- kazinator 9y ago> bluffing the interview "bluffer overflow vulnerability". :)