3 ms·
We actually did consider them briefly. The problem in this case was having zero in-house knowledge about the technologies nor anybody particularly experienced w
by jwilm 10y ago
We actually did consider them briefly. The problem in this case was having zero in-house knowledge about the technologies nor anybody particularly experienced with FP. We did not want to take on that much risk.
- im_down_w_otp 10y agoYou started with experienced Rust people? Where'd you find them? I'd _love_ to find a vein of them to mine over time. :-)
- stymaar 10y agoIt depends what are your requirements (how «experienced» you want them) but it shouldn't be too hard to find : - Rust is still a really young language and most of us just use it as a hobby and don't write Rust for a living, but many would love to. And for some of these people (I'm one of them), been able to use Rust at work can be a good reason to join you. - IMHO Rust is a good language for recruitment because - it has a high barrier to entry - you can't just fake knowing Rust: if a candidate doesn't understand the ownership system really well, he won't even be able to write a 100 lines code sample. To get in touch with potential candidates you could post on /r/rust, and I'm pretty sure it will be well received since many people are eager for Rust job opportunities. Of course if you need someone with 3 year+ professional experience with Rust, your choice will be a bit narrow ;)
- adrianN 10y agoPost in HN's "Who's hiring". Rust being constantly on the front page seems to be a good indication that there are many people here who are interested in the language.
- thenewwazoo 10y agoIndeed - I write things in Rust on my own time and enjoy doing it so much that I'd consider "come write Rust" to be a big, big positive differentiator between jobs.