When I proposed to my wife, I met her after a couple of years and didn't know at the time if she was seeing someone.
I nudged the conversation towards that topic and once I found out that she isn't, I literally proposed to her in office jargon.
I said, "So if the vacancy is still available, can I apply?". She said yes, and we got married eventually but she still isn't too happy about that proposal line.
We went to university together, had a semi-romantic friendship before as well. I always liked her and I thought she liked me back too but after graduating I was focused on other stuff, wasn't actively looking for a relationship. Hence the gap.
Recently applied at CataWiki and aced the actual coding problem, but was later rejected because I failed the 2 hours whiteboard part of the interview. I have to say, those hours in front of the whiteboard are really not pleasant and I would have performed much better if I had real-life problems to solve using real-life tools.
Sorry, but on second thought this reply only lists the negative side of my experience. On the positive side, CataWiki has been excellent in communication and sharing feedback throughout the process and they have a really nice office and great culture. Definitely a place I could see myself working at so the company itself is not bad, just that the whiteboard part of the interview process could be improved/replaced.
Location: Tallinn, Estonia
Remote: No
Willing to relocate: Yes
Technologies: typescript, node.js, react, ruby on rails (lots of small experiences in other technologies)
Résumé/CV: https://www.linkedin.com/in/ahmadarsalan/
Email: contact@arsalan{dot}me
I've spent most of my career (4.5+ years) in early stage startups and now I'm looking to move to a mid-sized company preferably working on a product having a positive effect on the world.
Guys, can't we just detect a program doing spectre-like behavior and just kill it instead of having every other application suffer a performance hit by the proposed changes? Antivirus software already does similar stuff
I develop an application that has a SPA frontend and an API backend. They can love inside separate repos but I prefer to keep them together because if I change the API signature, I'll also make the same changes in the frontend and they will deploy together at once.
I'd wait for the ecosystem to mature before building a business app with Phoenix. You never know what taken for granted library is missing in Elixir, and it's going to be damn hard to hire a developer experienced with Phoenix. Everyone on your team will be slow and will be making a steady stream of mistakes as they learn the framework
I think Phoenix (and Elixir) is mature enough already to use in production. I've made pretty good, bordering on oracle-like :) predictions about directions in technology over more years than I care to think about; so I'm confident that Phoenix is only going to grow in use and positive attention.
It will be the logical successor to Rails. It already is.
That said, I use a good mix of Elixir+Phoenix and old-school cron launched Python utility scripts, and that works nicely. Anything that's difficult (probably because I am still a newb) in Elixir I can easily do out of band with a Python script.
But your point about difficult to hire experienced people is the reason for my reply. This is the mentality that is ruining IT and development. Yes, having someone with hands on experience in all of your tools is nice - a rare luxury in fact. But it's really not necessary. I would be quite happy to have someone that has willingly built something in Rails, Django, and Nodejs with an "Oh I can learn that" attitude. Especially if you come from a modern MVC framework, Phoenix itself is easy. Elixir is the part that requires some real effort, imo.