<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for jfcouture</title><link>http://disqus.com/by/jfcouture/</link><description></description><atom:link href="http://disqus.com/jfcouture/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 27 May 2010 20:02:56 -0000</lastBuildDate><item><title>Re: Why didn't Jack die in the "Heart of the Island" like Jacob's brother?</title><link>https://lostpolls.blogspot.com/2010/05/why-didnt-jack-die-in-heart-of-island.html#comment-52477364</link><description>&lt;p&gt;1st theory: It was one last f u from Jacob to MIB. Jack being good and not corruptible is why he didn't turn into another smoke monster, and it meant Jacob won his 'bet' against the MIB that not all men are evil.&lt;/p&gt;&lt;p&gt;2nd theory: Jack does get a fate worse than hell, eternity with Kate ;)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Thu, 27 May 2010 20:02:56 -0000</pubDate></item><item><title>Re: The Key to Startup Hiring: Build a Magnet</title><link>https://www.instigatorblog.com/startup-hiring-build-a-magnet/2009/10/20/#comment-20650564</link><description>&lt;p&gt;As a ruby on rails developer here in Montreal, I've met a few startups in the last 2 months. I should probably write a full post about my experiences, but here's a few quick thoughts.&lt;/p&gt;&lt;p&gt;All your points are so very true. Startups, you need to market yourselves to prospective employees! It seems you expect developers to want to work for you, just because you're a startup. That's not how it works. And if you want top talent, guess what? Top talent probably has many other options too.&lt;/p&gt;&lt;p&gt;Also, if you're "under the radar" and have not built buzz yet, you need to tell me more about you want to build than just "it's about social networks". Working in a startup can be great, but you need to get me excited about the product.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Tue, 20 Oct 2009 16:55:28 -0000</pubDate></item><item><title>Re: Marty Haught</title><link>http://martyhaught.com/articles/2009/10/06/when-is-agile-too-much/#comment-19260181</link><description>&lt;p&gt;I like what you're saying. However, I'd argue that what you're describing is still agile. The term agile has been so much bastardized in the past few years that sometimes I don't know anymore what people are talking about when they use the term.&lt;/p&gt;&lt;p&gt;Pair programming is just one practice commonly used in agile processes, as is storycarding and automated testing. Agile at its core is a set of values and principles. You can be agile without those practices. And adapting your process to the context is definitively agile in spirit.&lt;/p&gt;&lt;p&gt;I think the real point of your article is that for a small, 1 man, 3 week part time project, you don't need much process to deliver.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Tue, 06 Oct 2009 18:29:17 -0000</pubDate></item><item><title>Re: To self. or not to self.</title><link>http://robots.thoughtbot.com/post/185504560#comment-16443793</link><description>&lt;p&gt;Actually, the reason I personally started using self almost everywhere is because of ActiveRecord. I use self to indicate that it's an attribute of the model that's defined in the database. I think I started doing it after inheriting a legacy app with huge models file. Everytime I needed to change something, I always had trouble finding where the method/attribute was defined or remembring if it was an attribute.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Fri, 11 Sep 2009 17:53:46 -0000</pubDate></item><item><title>Re: Ruby Best Practices - Fun with Class.new</title><link>http://blog.rubybestpractices.com/posts/gregory/anonymous_class_hacks.html#comment-8930475</link><description>&lt;p&gt;I'm sorry I wasn't clear. In general when defining errors class, 99% of the time you want to subclass StandardError and not Exception. You also generally don't want to catch Exception directly as this prevents from ctrl-c interrupt to gracefully exit. Also rescue =&amp;gt; e only catches StandardError.  Since this is a best pratice blog, I felt the need to point it out. It's a subtlety of exception handling in ruby that not everyone is aware of.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Sat, 02 May 2009 11:19:59 -0000</pubDate></item><item><title>Re: Ruby Best Practices - Fun with Class.new</title><link>http://blog.rubybestpractices.com/posts/gregory/anonymous_class_hacks.html#comment-8924387</link><description>&lt;p&gt;I think you want to use StandardError, like in the article, instead of Exception.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Sat, 02 May 2009 09:43:09 -0000</pubDate></item><item><title>Re: Tips for writing your own Rails engine</title><link>http://robots.thoughtbot.com/post/159805560#comment-14588569</link><description>&lt;p&gt;Have you asked the core team if these issues are expected behaviour? It might be nice to have these the default in future version of rails.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Fri, 24 Apr 2009 16:48:00 -0000</pubDate></item><item><title>Re: http://blog.rubybestpractices.com/posts/jamesbritt/2009-04-13-solving-the-problem.rc.html</title><link>http://blog.rubybestpractices.com/posts/jamesbritt/2009-04-13-solving-the-problem.rc.html#comment-8245578</link><description>&lt;p&gt;to james and sandal:&lt;/p&gt;&lt;p&gt;As a developer, I totally understand why you'd want to roll your own solution! :)&lt;/p&gt;&lt;p&gt;I'm in the process of updating my blog so I'm looking at different solutions. I was wondering if there was something about Webby that made it seem like a bad choice for this site.&lt;/p&gt;&lt;p&gt;But probably the thing that confuses me the most is why you're using grit. I mean it's natural to use git to version the text files of the posts, but when generating the site, why do you need to access the git objects, instead of working directly with the files?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Wed, 15 Apr 2009 20:16:30 -0000</pubDate></item><item><title>Re: http://blog.rubybestpractices.com/posts/jamesbritt/2009-04-13-solving-the-problem.rc.html</title><link>http://blog.rubybestpractices.com/posts/jamesbritt/2009-04-13-solving-the-problem.rc.html#comment-8241148</link><description>&lt;p&gt;I'm not sure I understand why you built Korma. What's the difference between Korma and using Webby along with git?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Wed, 15 Apr 2009 17:20:55 -0000</pubDate></item><item><title>Re: I'm Updating and Obsolescing Articles on My Blog &amp;mdash; A Single Programmer's Blog</title><link>http://blog.teksol.info/2009/04/02/im-updating-and-obsolescing-articles-on-my-blog.html#comment-7745804</link><description>&lt;p&gt;That's great. I think we should call this the Great Spring Cleaning!&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Thu, 02 Apr 2009 12:19:48 -0000</pubDate></item><item><title>Re: GiraffeSoft | Welcome to smarter web app development.</title><link>http://giraffesoft.ca/blog/2009/03/10/4-core-competencies-of-great-hackers.html#comment-7087627</link><description>&lt;p&gt;I said crappy analogy, and it's such a stupid point that I stopped halfway. But I did say that it was custom, which probably means the guy is gonna charge by the hour for his time. But maybe he's cheaper so it'll cost the same in the end. But if you need it quick, one guy will be better. (we could go on with the ifs, but the point is getting done efficiently, which in my example, would mean quicker and cost less for a carpenter).&lt;/p&gt;&lt;p&gt;But your reply sheds some light. You take things too personally. I did not assume you are inefficient. I said that you missed the point. This article is not about getting things done. It's kinda pointless to type 60 wpm and write a novel when you should be writing a program. The 4 points kinda assume that you are delivering working software. They're about moving from good to great. Also, another subtlety you have missed, if you reread the last paragraph, is that they did not say that you absolutely have to do these 4 things, or that they are the only 4, to be great.&lt;/p&gt;&lt;p&gt;This is the blog of a consulting company. They care about being as efficient as possible.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Tue, 10 Mar 2009 19:40:57 -0000</pubDate></item><item><title>Re: GiraffeSoft | Welcome to smarter web app development.</title><link>http://giraffesoft.ca/blog/2009/03/10/4-core-competencies-of-great-hackers.html#comment-7081900</link><description>&lt;p&gt;And I will go to my grave wondering why so many seemingly intelligent people get by in life without basic reading comprehension skills. :P&lt;/p&gt;&lt;p&gt;Nobody is saying to learn every shortcut of your text editor.&lt;/p&gt;&lt;p&gt;And getting things done is nice and all. However, maybe you will one day realize that there is a step after getting things done: getting things done efficiently.&lt;/p&gt;&lt;p&gt;And since you want to bring the hammer into play, I'm going to go along with a crappy analogy: let's say you want a custom piece of furniture. You visit two carpenters. Both have great things on display. However, you get a glance at how they work. One nails each nail in one hit. The other has shaky hands, needs to slowly hit not to hit beside the nail, and needs 2 mins for each nail.&lt;/p&gt;&lt;p&gt;And I want to sincerely apologize for being so snarky in this post. I just hate it when people dismiss something by mischaracterizing it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Tue, 10 Mar 2009 17:26:56 -0000</pubDate></item><item><title>Re: Plugins I've Known and Loved #2: has_finder</title><link>http://jamesgolick.com/2008/2/25/plugins-i-ve-known-and-loved-2-has_finder.html#comment-7965273</link><description>&lt;p&gt;has_finder is f awesome. I'm glad to hear it might make it into rails. When you start using it, there's no going back.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Mon, 25 Feb 2008 14:37:00 -0000</pubDate></item><item><title>Re: Plugins I've Known and Loved #2: has_finder</title><link>/2008/2/25/plugins-i-ve-known-and-loved-2-has_finder.html#comment-7962532</link><description>&lt;p&gt;has_finder is f awesome. I'm glad to hear it might make it into rails. When you start using it, there's no going back.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Mon, 25 Feb 2008 14:37:00 -0000</pubDate></item><item><title>Re: Introducing resource_controller: Focus on what makes your controller special.</title><link>/2007/10/19/introducing-resource_controller-focus-on-what-makes-your-controller-special.html#comment-7962257</link><description>&lt;p&gt;Interesting.&lt;/p&gt;&lt;p&gt;What's the difference between this and the make_resourceful plugin you presented at montreal on rails (except from a different api)?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Fri, 19 Oct 2007 14:47:00 -0000</pubDate></item><item><title>Re: Testing Misconceptions #1: Exploratory Programming</title><link>http://jamesgolick.com/2007/10/5/testing-misconceptions-1-exploratory-programming.html#comment-7964940</link><description>&lt;p&gt;Good article. A small nitpick however:&lt;/p&gt;&lt;p&gt;"Nobody is suggesting that you write your acceptance tests first."&lt;/p&gt;&lt;p&gt;Why not? I'd argue that acceptance tests are easier to write first as they are at a much higher level. While you may start with some exploration at the unit level for your design, you should already have an idea of what your customers expect from the application before hand.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Tue, 09 Oct 2007 22:44:00 -0000</pubDate></item><item><title>Re: Universities Need To Develop Entrepreneurs</title><link>https://www.instigatorblog.com/universities-need-to-develop-entrepreneurs/2007/05/21/#comment-1647839</link><description>&lt;p&gt;I may have been a bit harsh about intellectual curiosity, but I still have a hard time explaining why I couldn't convince more than 10% of the students in software or computer engineering to go to CUSEC.  I shouldn't even have to try.&lt;/p&gt;&lt;p&gt;But this makes me think that a good portion were interested in the gaming industry. Maybe the problem is that when they hear news about technology in Montreal, it's generally about a big company opening a studio here in Montreal (Ubisoft, EA). Maybe there just needs to be a couple of hot Montreal startups all over the news so that they can see entrepreneurship as a viable solution instead of working for one of the big ones.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Tue, 22 May 2007 22:23:56 -0000</pubDate></item><item><title>Re: Universities Need To Develop Entrepreneurs</title><link>https://www.instigatorblog.com/universities-need-to-develop-entrepreneurs/2007/05/21/#comment-1647842</link><description>&lt;p&gt;Some would argue that universities should start by teaching real world skills. I've had this discussion many time in university with faculty staff, and I guess the answer depends on what you think the role of universities is, or should be (professors would say it's research).&lt;/p&gt;&lt;p&gt;Most universities already offer most of the things you propose. At Polytechnique, there's a four course entrepreneurship option you can follow, they have a service to help students convert their school work (mostly for masters and doc) to a company. There is the HEC entrepreneurship center that gives conference on all subjects related to starting a company. Starting last year I think, all program require at least one internship. And there is already a contest that rewards the best idea for a company with some startup money. I guess the part they fail right now is experimenting with new technology, although some professors try from time to time in one of their class.&lt;/p&gt;&lt;p&gt;I think most student just lack intellectual curiosity. It's tough to try and convince most of them to come to a conference such as CUSEC, that is in their city, costs almost nothing (50$) and gives them world class speakers. And of those that do decide to come, half aren't bothered to take 5 minutes to check about a subject they don't know about, and they decide to not attend some very interesting talks.&lt;/p&gt;&lt;p&gt;I think Mat may be on to something about it being a cultural thing.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jfcouture</dc:creator><pubDate>Tue, 22 May 2007 13:32:11 -0000</pubDate></item></channel></rss>