Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 159

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 162

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 165

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 168

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 171

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 173

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 175

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 197

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 201

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 224

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 225

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 226

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 316

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 316

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 316

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 316
Montreal On Rails First Edition Report

Tuesday night saw the birth of the Montreal On Rails user group in a small room on the Mcgill campus. It was a lot of fun.

The first presentation was by Marc-André Cournoyer, Standout Jobs Ruby Guru, entitled “How to make your tests faster”.
Marc-André started with a very funny introduction. I don’t know how to describe his intro. He should turn it in a video for all to see. First part was a demonstration of caching results from external apis (he used twitter as an example) to a file to make tests go really fast on your development machine. You then add a flag so the build machine uses the actual api. You get the best of both worlds: fast tests when developping, but you also validate that the api didn’t change. I just started a project monday that is gonna connect to 3 apis, so the presentation was very timely.

The second part was about a plugin he is developping called InactiveRecord to stub out the access to the database for your test. You can find the slides to his presentation along with the code here.

Second presentation was from Carl Mercier of Karabunga. It was a small tutorial on HAML, a templating engine for Rails. You can play online with HAML here. The latest version released a couple of weeks ago seems to have fixed a lot of performance problem (30% slower than rhtml instead of 1000% slower). I will have to give it another try soon, along with sass, which is haml for css.

Suggestions for improvements:

  • Bigger room for more people, but also more open space to make it easier to socialize, and a room where donuts are allowed ;)
  • Wiki on montrealonrails.com so people can post suggestions for topics that would interest them for presentations
  • Maybe we can have a round of quick presentation (2-5 mins) if let’s say you want to present a small plugin or a ruby trick. This could help orient discussions after the main presentation. It would also allow more people to talk and present themselves, in a less intimidating way than a full blown presentation.
  • Maybe someone is crazy enough to want to videotape the presentations?

I can’t wait for the next edition!

Popularity: 23% [?]

 

4 Responses to Montreal On Rails First Edition Report

  1. macournoyer says:

    Thanks for the feedback J-F, I’m happy you liked my presentation and mostly that it was helpful to you!

    I agree with your suggestions, great ideas.

    Hope to see you at the breakfast next week!

    • Salim says:

      Posted on November 8, 2012 by I precisely nedeed to thank you very much yet again. I am not sure the things that I would have sorted out without the actual information revealed by you regarding such a area. This has been a real alarming problem for me, nevertheless taking a look at a new professional technique you processed that took me to cry for delight. I’m happier for this work and thus believe you know what a great job you happen to be getting into educating most people through the use of your website. Most likely you haven’t met any of us.

    • Ashok says:

      Posted on November 9, 2012 by I have got 1 recommendation for your wesbite. It looks like there are a number of cascading stylesheet issues while opening a number of web pages inside google chrome and safari. It is running okay in internet explorer. Probably you can double check that.

  2. [...] to other reports you can find in other montreal rails blogs, I won’t go into technical details. I [...]

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>