Posts Archive

"I just got a mail confirming that I will not speak at RailsConf Europe this fall. I had submitted a proposal named “Version Control in Rails using Mercurial” which was going to show the benefits of using a distributed version control system when developing a Rails app. My opening line would have been “Hi, I am Marcus and I have been Subversion free for six months”. For some weird reason, so many people in the Rails community - and the open source community as whole - still talk about Subversion as something great."

"Sitting in Stockholm reading blogs, it feels like being home on a friday night knowing that there is a great party going on and you are not going."

"I am using Ruby based DSL’s for a number of tasks in my current project. But one day it struck me - am I using the right tool for the job, could there be a better, more simple solution? Some DSL’s I use are simply declarative and look something like this: quiz "Let's ask stuff" do question "What is 1+1?" do alternative "2", :correct => true alternative "3" end question "Vad is 2+3" do alternative "1" alternative "Infinity" alternative "Don't know" alternative "5", :correct => true end end I find that quite readable, but it requires me to maintain code that handle the DSL."

"Last time I quoted Neal I for some reason ended up on TheServerSide why they did not link to Neal directly is beyond me. Oh well, he is obviously on a roll, I totally love this one: Static Typing is Communist Bureaucracy (Via Planet TW.)"

"I just noticed that the mapping between PostgreSQL’s Time Without TimeZone column type maps to Rubys standard Time class. Which gives the following behavior in script/console: :::ruby >> t = TimeEntry.find(1) >> t.time => Sat Jan 01 23:00:00 +0100 2000 >> t.time = Time.now => Wed May 09 19:02:07 +0200 2007 >> t.save => true >> t = TimeEntry.find(1) >> t.time => Sat Jan 01 19:02:07 +0100 2000 Am I very anal to find this … sloppy?"

"Some time ago, there was a lengthy debate on the Agile Sweden mailing list regarding the term “Architect”, and what it means. My position is that the term has become synonymous with the paper or PowerPoint architect, and I therefore try to stay clear of it. Other people haad other opinions. Neal Ford has changed his title, and describes why in a brilliant way: Neal Ford: From Architect to Wrangler: […] “The title of ‘Architect’ for software developers has gotten so diluted that its meaningless anymore."

"Reading this a little bit earlier would have saved me a lot of time. In short: callbacks such as :before_add does not work with has_many :through, and the documentation does not tell you that. To get callbacks, add them to the join model."

"Paul Duncan is another Mercurial convert, and explains his choice of VCS very well"

"The current incarnation of autotest seems to assume that you are using integrated views. If not, you can modify the rspec_rails_autotest.rb file to run the view specs as well: :::ruby # when %r%^app/views/layouts/(.*)\.rhtml% then # ["spec/views/layouts/#{$1}_spec.rb"] when %r%^app/views/(.*)\.rhtml$% then ["spec/views/#{$1}_view_spec.rb"] Your view spec must be postfixed with “_view_spec.rb” for it to work Update This works out of the box now."

"Autotest 3.5.0 is out, and the result given from Autotest is no longer a String, it’s an array of strings. So if you still want Growl to function properly just modify the .autotest slightly: #ruby module Autotest::Growl def self.growl title, msg, img, pri=0, stick="" system "growlnotify -n autotest --image #{img} -p #{pri} -m #{msg.inspect} #{title} #{stick}" end Autotest.add_hook :ran_command do |at| output = at.results.last.slice(/(\d+)\s.*specifications?,\s(\d+)\s.*failures?/) if output =~ /[1-9]\sfailures?/ growl "Test Results", "#{output}", '~/Library/autotest/rails_fail."