<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Adam @ Heroku: Comments</title>
    <link>http://adam.blog.heroku.com</link>
    <language>en</language>
    <webMaster>adam@heroku.com (Adam Wiggins)</webMaster>
    <copyright>Copyright 2007-2008</copyright>
    <ttl>60</ttl>
    <pubDate>Tue, 22 Jul 2008 11:41:53 GMT</pubDate>
    <description>a tornado of razorblades</description>
    <item>
      <title>How embarrassing - updated....</title>
      <link>http://adam.blog.heroku.com/past/2008/7/22/dude_that_is_so_fringe/#c220</link>
      <pubDate>Tue, 22 Jul 2008 11:41:53 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/7/22/dude_that_is_so_fringe/#c220</link>
      <author>Adam Wiggins</author>
      <description>&lt;p&gt;How embarrassing - updated.&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/7/22/dude_that_is_so_fringe/"&gt;Dude, That Is So Fringe&lt;/a&gt;</description>
    </item>
    <item>
      <title>Yueda Katz = Yehuda Katz...</title>
      <link>http://adam.blog.heroku.com/past/2008/7/22/dude_that_is_so_fringe/#c219</link>
      <pubDate>Tue, 22 Jul 2008 09:37:50 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/7/22/dude_that_is_so_fringe/#c219</link>
      <author></author>
      <description>&lt;p&gt;Yueda Katz = Yehuda Katz&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/7/22/dude_that_is_so_fringe/"&gt;Dude, That Is So Fringe&lt;/a&gt;</description>
    </item>
    <item>
      <title>interesting re-cap of Reginald Braithwaite's...</title>
      <link>http://adam.blog.heroku.com/past/2008/7/22/dude_that_is_so_fringe/#c218</link>
      <pubDate>Tue, 22 Jul 2008 07:58:04 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/7/22/dude_that_is_so_fringe/#c218</link>
      <author>josh</author>
      <description>&lt;p&gt;interesting re-cap of Reginald Braithwaite's talk given that he just blogged he's retiring from blogging and ruby hacking.&lt;/p&gt;

&lt;p&gt;http://weblog.raganwald.com/2008/07/brief-history-of-dangerous-ideas.html&lt;/p&gt;

&lt;p&gt;btw, living in the fringe is where you get to test and hone concepts that become practical technology.  It's fun because of the growth you undertake and the opportunity to contribute things. in my opinion.&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/7/22/dude_that_is_so_fringe/"&gt;Dude, That Is So Fringe&lt;/a&gt;</description>
    </item>
    <item>
      <title>Hey am getting 500 error...</title>
      <link>http://adam.blog.heroku.com/past/2008/7/16/rush_04/#c217</link>
      <pubDate>Fri, 18 Jul 2008 04:54:37 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/7/16/rush_04/#c217</link>
      <author>Ketan</author>
      <description>&lt;p&gt;Hey am getting 500 error on rush.heroku.com now.
would be using it on my ubuntu machine soon&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/7/16/rush_04/"&gt;rush 0.4&lt;/a&gt;</description>
    </item>
    <item>
      <title>Totally agree. I think it...</title>
      <link>http://adam.blog.heroku.com/past/2008/7/14/owning_up/#c216</link>
      <pubDate>Thu, 17 Jul 2008 13:52:28 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/7/14/owning_up/#c216</link>
      <author>Alan Brown</author>
      <description>&lt;p&gt;Totally agree.  I think it makes sense to also make it predictable for doctors what the consequences are for their mistakes, instead of having a jury come up with something.&lt;/p&gt;

&lt;p&gt;Even more important is accurate data regarding outcomes for certain procedures NOT reported by doctors themselves but gathered independently.  &lt;/p&gt;

&lt;p&gt;Also good would be to have some separation from assessment and delivery.  Thee is a natural conflict of interest when the person who will be paid to deliver solutions is also decidng whether those solutions are needed.  I guess that was the idea initially behind the primary care physician, but something got lost along the way.&lt;/p&gt;

&lt;p&gt;Regarding software developers, there are no real liability concerns from admitting mistakes, so only the ego stands in the way.  &lt;/p&gt;

&lt;p&gt;Not comparable at all to the back surgeon acknowledging, "Oh yeah, looks like this surgery has left you with even more pain.  Sorry about that.  Have a nice life." &lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/7/14/owning_up/"&gt;Owning Up&lt;/a&gt;</description>
    </item>
    <item>
      <title>Hi, class Book class Author...</title>
      <link>http://adam.blog.heroku.com/past/2007/12/20/nested_resources_in_rails_2/#c214</link>
      <pubDate>Fri, 11 Jul 2008 03:57:38 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2007/12/20/nested_resources_in_rails_2/#c214</link>
      <author>Advait </author>
      <description>&lt;p&gt;Hi, &lt;/p&gt;

&lt;p&gt;class Book &amp;lt; ActiveRecord::Base
  belongs_to :author
end&lt;/p&gt;

&lt;p&gt;class Author &amp;lt; ActiveRecord::Base
  has_many :books
end&lt;/p&gt;

&lt;p&gt;And I am using&lt;/p&gt;

&lt;p&gt;before_filter :abc
def abc
  @author = Author.find(params[:author_id])
end&lt;/p&gt;

&lt;p&gt;I am getting an error "Couldn't find Author without an ID"&lt;/p&gt;

&lt;p&gt;How do I correct this as I have no idea about this&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2007/12/20/nested_resources_in_rails_2/"&gt;Nested Resources in Rails 2&lt;/a&gt;</description>
    </item>
    <item>
      <title>Anyone have any instructions for...</title>
      <link>http://adam.blog.heroku.com/past/2008/6/17/battling_wedged_mongrels_with_a/#c213</link>
      <pubDate>Thu, 10 Jul 2008 08:00:34 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/6/17/battling_wedged_mongrels_with_a/#c213</link>
      <author>Dan</author>
      <description>&lt;p&gt;Anyone have any instructions for Merb and/or Rack handlers?&lt;/p&gt;

&lt;p&gt;In my first attempts to use this library I tried to wrap the call in a begin/rescue block.  I wanted to explicitly rescue Timeout::Error so I could return a 504 Gateway Timeout error to the client.  However I seem to be unable to rescue the exception.&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/6/17/battling_wedged_mongrels_with_a/"&gt;Battling Wedged Mongrels with a Request Timeout&lt;/a&gt;</description>
    </item>
    <item>
      <title>Thanks! This took some guess...</title>
      <link>http://adam.blog.heroku.com/past/2007/12/20/nested_resources_in_rails_2/#c212</link>
      <pubDate>Wed, 09 Jul 2008 01:29:41 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2007/12/20/nested_resources_in_rails_2/#c212</link>
      <author>Chris</author>
      <description>&lt;p&gt;Thanks! This took some guess work out of my work. Interesting idea about writing a generator. Maybe I'll get to that someday.&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2007/12/20/nested_resources_in_rails_2/"&gt;Nested Resources in Rails 2&lt;/a&gt;</description>
    </item>
    <item>
      <title>This is why I wish...</title>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c211</link>
      <pubDate>Tue, 08 Jul 2008 09:56:09 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c211</link>
      <author>pete</author>
      <description>&lt;p&gt;This is why I wish Heckle was a little more robust/well-used. It seems like it would be a great boon to the test-driven workflow, if only it weren't so finicky.&lt;/p&gt;

&lt;p&gt;http://ruby.sadi.st/Heckle.html&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/"&gt;The End of Bugs?&lt;/a&gt;</description>
    </item>
    <item>
      <title>Great. Thanks, Adam....</title>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c210</link>
      <pubDate>Mon, 07 Jul 2008 21:19:19 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c210</link>
      <author>marktucks</author>
      <description>&lt;p&gt;Great. Thanks, Adam.&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/"&gt;The End of Bugs?&lt;/a&gt;</description>
    </item>
    <item>
      <title>@marktucks - There are a...</title>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c209</link>
      <pubDate>Mon, 07 Jul 2008 20:19:05 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c209</link>
      <author>Adam Wiggins</author>
      <description>&lt;p&gt;@marktucks - There are a lot of diverse opinions on the best way to write specs/tests, what framework to use, etc.  I blog about this quite often, as you can tell: http://adam.blog.heroku.com/past/tags/bdd  Reading through these should answer some of your questions, at least from one person's perspective.&lt;/p&gt;

&lt;p&gt;Some other Ruby-centric resources on the subject I recommend:&lt;/p&gt;

&lt;p&gt;http://blog.hasmanythrough.com/2008/6/1/the-great-test-framework-dance-off
http://blog.jayfields.com/
http://blog.davidchelimsky.net/&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/"&gt;The End of Bugs?&lt;/a&gt;</description>
    </item>
    <item>
      <title>Is RSpec the de facto...</title>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c208</link>
      <pubDate>Mon, 07 Jul 2008 18:32:02 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c208</link>
      <author>marktucks</author>
      <description>&lt;p&gt;Is RSpec the de facto test framework i.e. what everyone is using, like Git?&lt;/p&gt;

&lt;p&gt;Also, are there any really comprehensive test tutorials, including things like what to test, how to test, code coverage etc?&lt;/p&gt;

&lt;p&gt;Thanks.&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/"&gt;The End of Bugs?&lt;/a&gt;</description>
    </item>
    <item>
      <title>Harlan Mills at IBM worked...</title>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c207</link>
      <pubDate>Mon, 07 Jul 2008 15:39:43 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c207</link>
      <author>JS</author>
      <description>&lt;p&gt;Harlan Mills at IBM worked on useful methods of software engineering called "cleanroom software engineering".  By the mid-70s they basically worked out how to build software that is provably correct by design at no additional cost beyond conventional software development methods.  Comparing that to the present day methods of programming, we've regressed considerably in the last 30 years across most of the industry.  More info can be found here if you're interested: 
http://www.sei.cmu.edu/str/descriptions/cleanroom.html&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/"&gt;The End of Bugs?&lt;/a&gt;</description>
    </item>
    <item>
      <title>"Nearly all developers, myself included,...</title>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c206</link>
      <pubDate>Mon, 07 Jul 2008 10:35:55 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c206</link>
      <author>andrew</author>
      <description>&lt;p&gt;"Nearly all developers, myself included, spend most of our time in that state: not quite trusting that the code all works"&lt;/p&gt;

&lt;p&gt;Fantastic quote.  In ten years of development, no matter how amazing the code, or tests, this is our state of mind.  I'm always amazed when things work the first time.&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/"&gt;The End of Bugs?&lt;/a&gt;</description>
    </item>
    <item>
      <title>If a bug is a...</title>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c205</link>
      <pubDate>Mon, 07 Jul 2008 09:46:39 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c205</link>
      <author>ngvrnd</author>
      <description>&lt;p&gt;If a bug is a variance from spec, and the behavior you observed was from code which wasn't spec'd, was it a bug?  Maybe an additional definition is needed; any code which isn't covered by the spec is also a bug.&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/"&gt;The End of Bugs?&lt;/a&gt;</description>
    </item>
    <item>
      <title>Who was testing your app...</title>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c204</link>
      <pubDate>Mon, 07 Jul 2008 06:23:11 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c204</link>
      <author>Stephen Waits</author>
      <description>&lt;p&gt;Who was testing your app all that time?&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/"&gt;The End of Bugs?&lt;/a&gt;</description>
    </item>
    <item>
      <title>Interessant ideas. Ohh and THANK...</title>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c203</link>
      <pubDate>Mon, 07 Jul 2008 05:18:07 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c203</link>
      <author>Paul</author>
      <description>&lt;p&gt;Interessant ideas.&lt;/p&gt;

&lt;p&gt;Ohh and THANK YOU for havinf formulating this : "Nearly all developers, myself included, spend most of our time in that state: not quite trusting that the code all works.". That's SO TRUE (IMHO too, at least)!&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/"&gt;The End of Bugs?&lt;/a&gt;</description>
    </item>
    <item>
      <title>Thanks guys. I thought this...</title>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c202</link>
      <pubDate>Mon, 07 Jul 2008 04:29:27 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c202</link>
      <author>Adam Wiggins</author>
      <description>&lt;p&gt;Thanks guys.  I thought this post would be more controversial - glad to hear I'm not alone on this. :)&lt;/p&gt;

&lt;p&gt;Now, playing devil's advocate to myself here, specs can only extend so far - i.e. to the edges of the component they belong to.  In a service architecture there's still the interaction between components.  I'm starting to develop some techniques to cover that, but it's a very different sort of thing.  No doubt I'll post about that stuff at some point.&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/"&gt;The End of Bugs?&lt;/a&gt;</description>
    </item>
    <item>
      <title>Absolutely! This is why debugger...</title>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c201</link>
      <pubDate>Mon, 07 Jul 2008 04:15:22 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c201</link>
      <author>Giles Bowkett</author>
      <description>&lt;p&gt;Absolutely! This is why debugger support is a bad thing. Development practices which are very close to bug-proof exist.&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/"&gt;The End of Bugs?&lt;/a&gt;</description>
    </item>
    <item>
      <title>Although I've been a TDD...</title>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c200</link>
      <pubDate>Mon, 07 Jul 2008 03:52:53 GMT</pubDate>
      <link>http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/#c200</link>
      <author>josh</author>
      <description>&lt;p&gt;Although I've been a TDD supporter for years, I hadn't yet learned BDD. I've been thinking its something I should do, and now I'm convinced. Thanks.&lt;/p&gt;&lt;p&gt;Posted to: &lt;a href="http://adam.blog.heroku.com/past/2008/7/6/the_end_of_bugs/"&gt;The End of Bugs?&lt;/a&gt;</description>
    </item>
  </channel>
</rss>
