The biggest advantages of io-ts over the jsonschema based type generation approach is that our data doesn't have to be json and we can handle non-serializable and complex data structures eg. class instances etc.
This makes it additionally useful for scenarios where we are writing a typescript library but also want good descriptive error messages for users who use vanilla javascript.
Even for type-checking at io boundaries [1], it is more useful than jsonschema because using io-ts we can, besides validating the data, also transform our incoming and outgoing data into richer data-structures (eg. string <-> date instance, plain javascript objects <-> class instances) through use of encoders and decoders.
While these items might be true, as an interviewer you are not trying to solve for “find all good candidates” but, instead, are solving for “find one good enough and better than the rest”.
Anymore, I love that I have a clear path on how to obtain a very high six figure gig with plenty of resources to get there. I’ll gladly play that game, with enthusiasm. When others focus on the plight of the interviewee, others are leetcoding, white-boarding, practicing, reading up on blind, etc.
Depends, I don't think you care all that much about coding skills. You don't want a cripple, but you want a diva even less. You can take a learning developer with an amazing passion for learning, and building shit while you must refuse a guy who say he's leet coding and shit on everyone trying to learn from him :D
Depends what industry you work in, but where I am, it's more about accepting to switch team and language during hiring freeze, spend a week or two on legacy retro spec'ing, tell business users that you failed your impossible deadline, and fix your own crap honestly. Nothing leet about it, just brutal honesty, courage and loyalty to get a six figure where I am.
Long term job and total comp prospects. Having done tacked on FP in Node.js (Fantasy Land, Sanctuary, Ramda) and Scala (scalaz, cats) for quite some time and now programming in "proper" FP languages like PureScript and Haskell daily, I absolutely love life as a programmer.
However, having a decent sized family with deep roots, wanting to do college for my children as a sole earner, not living near a tech-hub of any sort, I come away with this wish list -- and I have to sustain for 20 to 30 years. ~150k TC, remote, FP languages, for the net 20 to 30 years. Seems like a tall order. We could add up all the FP Scala, FP JS, Clojure, Rust, Haskell, PureScript, Elm, OCaml, ML, etc gigs and it would be a sliver compared to the prospects of just picking the same list with just any of the other top 10 languages.
I could hop into a remote Node.js/Scala gig and slowly sell them on FP, but having done this for the past few years it gets a bit draining to fight over small FP items when you are ready to do so much more.
Statically typed functional programming. I see plenty of Haskell, PureScript, ocaml, Scala (used functionally), and other language engineers who appear to be over 40.
