hitonagashi

Yeah, I am - eng lead at Shopify here and actively hiring. What were you wondering? :-)

No, that's not entirely correct.

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.

Except for the fact that none of the people who would give me the updates I'm interested in are on Google+...

The judge isn't disputing that.

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.

I hit this with Pixelmator...I actually assumed it was their fault, and just uninstalled it and reinstalled it again, after which it worked fine.

I'm on Snow Leopard still though, so might not just be a Lion problem.

If you go to an artist, you can also select an artist radio. Select the artist, and it's in the top tabs to the right.

:(.

Using Whenever and Whenever (ruby cron gem) together will make my head pop.

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.

Spotify is one of two applications that my family have discovered and use regularly without me recommending it. The other is Dropbox.

Agreed on this. I've filed 2-3, and each has had a reply in minutes.

I believe it just executes the javascript on that tab. Navigate away from the page to 'uninstall' it.

Great extension!

You don't hear about the 99% of the attempts that were successfully foiled by good coding practices/security audits, so given that we are hearing about a security breach at a competent firm, the likelyhood of it being a black swan event is probably fairly high.

Rudimentary version control?