Test:
class GroupsController < ApplicationController
def index
@group = nil
end
end
Not working...

Looking for a job that can rock my world. Must allow me to be productive on a daily basis. Rails preferred.
Would require tools that would automagically run integration tests and provide colorful bars and emoticons indicating where I did good and where I should focus on to improve, because I'm a color-code loving sucker.
Git would be lovely.
Team would be crazy results oriented. Never say "can't do it", always "what do we need to do to make it happen?" It would be great if they wanted to be famous for doing good things.
Ideally, there would be a multitude of challenges to best make use of my different skills and interests. I can haz variety. I would love opportunities to work out business logic for innovative products or services. It would be beneficial for both of us if you didn't mind my giving input into your marketing strategy and usability concepts.
Wow! I was sitting next to the hottest guy at IgniteBoston!
I was getting the error below when running a rake task. Which meant I couldn't rebuild my database. In specific, I started getting the error after freezing the ruby-net-ldap gem:
mm157859-pc:app carlisia$ rake (in /Users/carlisia/development/surveyengine)
ERROR:
Please update
/Users/carlisia/development/surveyengine/vendor/gems/ruby-net-ldap-0.0.4/init.rb
with the require path for linked RubyGem ruby-net-ldap
When I followed what the error message was informing and looked at the init.rb file, I noticed that none of the strings in the"require_options" array matched what was in my local directory. The two original strings to search for were "ruby-net-ldap" and "ruby/net/ldap":
However, my directory layout required a string search like so: "net/ldap":
I changed one of the elements in that array to "net/ldap". That took care of this problem.
The main message I took home from last night's #bostonrb meeting is that when moving to Ruby 1.9 a lot of things will inevitably break, because some of the changes are not going to be backwards compatible. So even if you sanitize your code, think about all the gems and plugins you are using: will they have sanitized their code too? And how will THEY keep backwards compatibility?
This last question was raised at the meeting and there was no good answer. The option that prevailed was to keep two separate files and load the one that corresponds to the running version.
It was emphasized that it will be crucial to have a good test coverage when making the transition. It will probably be a good idea having a plan to get your code ready.
1.9 is being frozen at the end of this month, and is slated to be release on 12/21.
Other than that backwards compatibility issues, 1.9 will:
Bruce Williams (@wbruce)was the person who presented the new Ruby 1.9. He has a tool that will let you compare the results of running code in 1.8 x 1.9 here, it's pretty cool:
http://github.com/bruce/compare-1-9/tree/master
+ a post from his blog on 1.9:
Arrow Lambdas, a Ruby 1.9 Vignette
Here is a pdf version I dugg out of Bruce's Ruby 1.9 presentation that is dated around April/2008.
The other presenter, Francis Hwang, also had some interesting stuff. He talked about some very interesting dynamic programming gotchas. Unfortunately, the link to his presentation pdf file doesn't work, only a link to an mp3 recording of a previous presentation on the same topic, "The API Construction Set":
If any new pdf files from this meeting gets posted to the bostonrb mailing list I will update this post with links to them.
I can't neglect to mention that the meeting, as always, was hosted by Sermo, which provides not only a nice space but also amazing food. And they are hiring tons.