2,167 karma · joined October 25, 2014
Are you talking about cash back? If so Amex does offer cards that support cash backs (I've had one for quite a few years). If you are talking about savings accounts, Amex also offers a High Yield Savings account whose rates are very competitive with other banks in the US.
When I interviewed at my current employer they made it very clear that the take home was meant as a conversation starter, and everyone who gets a take-home made it to the on-site (virtual in this case since its a remote role). This removed the guess work into whether the test will be a waste of time, as there was a guaranteed on-site interview. The test itself was also a more accurate representation of a simpler version of problems that the team was working on, as opposed to a generic algorithm problem.
Overall this was the most positive interview loop I've ever bene through, and was a big factor in making a decision to say yes to the job offer.
I use pyright at work at my current job, and used mypy at my previous job. Pyright has been better in almost every aspect in my experience. Its been more robust, and performs a lot better than mypy at type-checking in a fairly large mono-repo.
[1] Software and Updates is the app's name I believe.
EDIT: https://discuss.ocaml.org/t/multicore-ocaml-september-2021-e... is a forum post that goes into more detail about the state of effects in OCaml 5.0
[2] https://marketplace.visualstudio.com/items?itemName=ocamllab...
[3] https://discuss.ocaml.org/t/the-road-to-ocaml-5-0/8584
[4] https://github.com/ocaml-multicore/eio
[5] https://github.com/anuragsoni/sandbox/tree/main/ocaml/effect...
[1] https://microsoft.github.io/language-server-protocol/
[2] https://github.com/ocaml/ocaml-lsp/
[3] https://marketplace.visualstudio.com/items?itemName=ocamllab...
Same! I've made the mistake of overlooking certain things just because I wanted to get some real world OCaml experience in the past, and I will not make the same mistake again.
At my current job I mostly use OCaml and Python, with some Typescript for whenever I need to touch a frontend application. As much as I like using OCaml, I'm more thrilled about working on a team where I enjoy working with everyone, and having a work environment that provides flexibility about picking the best tool for a job. Most of my OCaml hacking still takes place on my free time, and on my personal open-source explorations :-)
> Thanks for the response!
You are welcome! Sorry if my responses weren't too useful with respect to using OCaml at work.
> it but it seems like there are very very few jobs that use it primarily.
I completely agree. I never tried looking for an OCaml job mostly because there weren't enough options at-least in the US (I'm based in USA), and I am picky about who I work for and wasn't interested in exploring job opportunities at companies working on cryptocurrencies. I just got lucky that I stumbled upon two different companies that used OCaml. The first time around I applied for the job because of OCaml, the second time around it was because I liked the company and OCaml was an added bonus on top.
Very true! I've used mutations and imperative OCaml quite a few times. Sometimes it was for performance reasons (I've been working on a web server library), and other times when loops either made the implementation a little easier to read, and/or helped avoid some allocations. I am glad that the language is pragmatic enough that I can still use mutation or imperative code where it makes sense, while still being able to present a nice clean api on top.