142 karma · joined September 29, 2009
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.
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.
I'm on Snow Leopard still though, so might not just be a Lion problem.
Using Whenever and Whenever (ruby cron gem) together will make my head pop.
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.
Great extension!
For example, the acorn pattern(http://en.wikipedia.org/wiki/File:Game_of_life_acorn.svg) is a lot more impressive, because the gliders spawned travel across the screen and interact with the solid blocks. Empirically, it seems to make the pattern last a lot longer!
Logically, all I needed to do was take a deep breath and move my foot sideways, but all I could think about was pulling up, which of course only exacerbated the problem.
It's not easy to think rationally when you are driving a car with several people accelerating when it should be breaking...and in the case of the linked story, it's not easy to accept blame either.
I can see so many ways that that can go wrong. To me, the reason it works seems more like peer pressure than enjoyment of work.
I love what I do, I love coding, and I also know that I love taking a week out to not care about everything I do at work. If I was in a system like that, I'd feel kinda pressured to keep up with my colleagues and not let the team down. Not by my friends and officemates, but by the knowledge that if I take a week off, that's a week they've got to handle the work I'd do. There's rarely a 'good' time to take holidays, especially in smaller teams.
It could work, it is certainly possible, but it seems an unnecessary area where pressure can occur when a team is under stress. To be honest, I think it could work better with the caveat that everyone has to take a certain minimum level of holiday.
Sick days however make perfect sense.
You can become great at anything with practice, I do believe that.
What I don't believe is that there's no such thing as talent. Take chess. You really think Magnus Carlsen has practiced less in his life than Anand? Practice is necessary to become great. Talent is necessary to become the best.
The cost is worth the fact that I find the articles much more...enjoyable(I'm not entirely sure that's the best word!).
Connection problems aside, I have been satisfied with the service. If I hadn't been a Times reader before, I don't think there's anything there that would persuade me to pay for it, but to me, the cost is worth it.
Good job that article pointed out that deleting and readding the alarm didn't fix anything.
It could be that if the angels are less certain of whether a company can balloon, they demand the more exact valuation in the theory of making that a x10 portfolio member..