Oh, hey! First of all, kudos for already having the career site reflecting the transition to "Digital by default". Just yesterday I was looking at the site and there was still different sections based on location.
My question is about the "Expression of Interest" positions that are listed. Are they used mostly as way to collect CVs from no-exact-match candidates, or could this be the channel for someone that, e.g, is working on an open source project that might align well with Shopify's interests?
If you prefer to answer by email, feel free to write me, lullis at google's mail.
You can do @user.public_keys.find(params[:id]).update_attributes(:user_id => 25)
Its the mass assignment protection on foreign keys that prevents you assigning one of your public keys to someone else, ensuring the chain is correct doesn't necessarily help with this scenario.
The right way is relative. I was never taught to touchtype, but I end up spending hours every day typing, so it just developed naturally.
Looking at the natural resting place of my fingers, I do use the F and J keys for resting my index fingers, but I'm pretty sure that there are faster ways of touchtyping than the methods I use.
He's saying that it is necessary to face a trial to determine it, and he isn't going to just brush the charges away and say they were definitely nothing. He's saying there's enough uncertainty that there should be a trial to answer it.
What's odd is that they only want to question him. Can't they question him, and if they don't like the answers, then extradite him? It all sounds a little odd to me.
I would just say, "I'm not going to answer your questions, so save yourself the cost of the flight and arrest me when you get some evidence."
This is something which has been brought up here in Sweden by people with legal background:
First the prosecutor at call (Marianne Ny) decided to arrest Julian Assange on the accusations from the two women. Meanwhile the news of his arrest has somehow been leaked to Expressen (a daily newspaper) the same evening.
Next day the chief prosecutor dismisses the case, this should have been the end of it.
However once Assange leaves the country, Marianne Ny (prosecutor on call) brings up the case again, and somehow manages to have Assange arrested on suspicion of rape, sexual assault, and has issued a european arrest order in order to question him.
This makes no sense, Marianne Ny says that the purpose of the international arrest is to 'question him', why couldn't she do that while he was still in Sweden? Why turn down the offers to question him on video conference or at an embassy in England BEFORE extraditing him given that Marianne Ny herself says that she doesn't have enough evidence to prosecute Assange and only wants to hear him at this time? Also given the huge costs that an 'international arrest order' brings along, to do so for questioning a suspect in such a weak case as this is unprecedented.
1) Agreed. Fully. Of my outside work time messing around on projects and such, 50% is reading HN, 50% is experimenting with new Rails plugins, or Ruby gems, or databases. I find on average, I end up finding something I prefer every 1.5 years as well.
2) Disagree here. Sure, you can't forget about it, but Rails 2 is perfectly useable. I'm currently managing a fairly substantial mix of Rails 2 and Rails 3 apps for various clients. If 2.3 works fine for them, and they want a minor feature every few months, it's just not worth the cost to them to upgrade. Sure, if major security holes emerge, patch and upgrade.
3) Agreed. I have a big gap between "things I play with on personal projects", and "things I'd use when I'm being paid at work". When I'm writing things for a client, I want battle tested code that I can predict against. I want to be able to say "That will take me a week", so I can bill, without the risk of going overbudget. If I take a new and shiny framework, and as a result of bugs in their code, or lack of documentation/6 month old blog posts being totally redundant and wrong, I end up slipping on the deadlines, that's not a situation I want to be in.
The thing that I really like is that Rails 2.x worked. I've got github, which stores old versions of gems and plugins for me to grab. I love Rails 3, and I teach new developers on it all the time, as I think it's far easier to learn and far more intuitive than Rails 2, but with Rails, I can take advantage of a fast moving easy to write system on new projects, while not getting screwed over on the old ones.
