Sometimes... stuff happens |
I am a father, husband, son, friend, software developer who loves Ruby, and an unemotional robot ( or at least that's what I've heard ). |
Quick tip: When using the same repo on multiple Heroku apps, such as staging, qa, production, you can pass a flag to heroku gem commands so that they are specific to the environment you want.
ie: heroku logs --app staging
Just pass the —app flag along with the name of your app on heroku (in this case the name of the app would be ‘staging’)… there you go. App specific logs. Or whatever it is you wanted.
Do you even realize how many hotdogs you have to eat to earn one of these? I don’t know the exact number, but the answer rhymes with “heart attack”.

As a software developer there are many different realms of knowledge that are necessary to be perceived as successful. There is so much information, even in one particular aspect, to be processed that even super brained comic book characters couldn’t keep up. So why do some feel it necessary to know everything? Not only that but get upset at themselves for not knowing. I understand having a competitive drive to be the best but knowing everything is just out the realm of possibility.
There is a good majority of days that I feel like a complete idiot for not knowing something till i realized that it is ok not to know. That is the beauty of working in a team or in a pair programming environment. Someone is bound to be in the know enough to help. When I don’t know something, I try to figure it out quickly and if it’s just not happening I will ask someone else. Come on guys, even with your gps powered techno devices… It’s ok to stop and ask for directions sometimes.
Actually not knowing something tends to be more satisfying for me because I love learning. Plus, more often than not I will figure it out on my own with a little extra time, when I do it’s like kicking the Hulk in the testicles. I feel like “F, right I just did that. Did you all see that? That was me.”
It’s the small wins that really count for me. I’d like to consider myself a “Jack of a moderate amount of trades, master of some (every once in a while)” and I hope you all do too. Not sure if this article amounts to much more than an incoherent rant but I hope that some of you take away that it’s cool to not be in the know on every subject.
Besides not liking the syntax, yet another reason to not use #update_attribute.
It doesn’t run validations. This is news to me… anyone else?
This has actually been tripping me up a bunch lately on new rails3 projects. I’m glad I stumbled across this because it does make everything easier. As in I don’t have to root around for that rspec.rake file I had in another project.
I’m sure someone out there has had this problem too… hope this helps.