A Fresh Cup is Mike Gunderloy's software development weblog, covering Ruby on Rails and whatever else I find interesting in the universe of software. I'm a full-time Rails developer and contributor, available for long- or short-term consulting, with solid experience in working as part of a distributed team. If you'd like to hire me, drop me a line. I'm also the author of Rails Rescue Handbook and Rails Freelancing Handbook.

Navigation
« Double Shot #440 | Main | Double Shot #438 »
Monday
27Apr2009

Double Shot #439

Note for future: do not allow all deadlines to match up at month-end.

  • Heroku Pricing - It's out, for a variety of shared and dedicated servers.

  • Internbot Chronicles #3 - Nick Quaranto surveys his corner of the testing universe.

  • Introducing Garb: Access the Google Analytics Data Export API with Ruby - THat didn't take long.

  • How Rails Works #2: Mime Types & respond_to - Internals analysis from Ryan Bigg.

  • How the OAuth Security Battle Was Won, Open Web Style - Twitter deserves serious love for their part in handling the situation.

  • Dear Fellow Rubyists - Audrey Eschright comments on women and marginalization in the Ruby community. I utterly deplore some of the drive-by juvenile comments this discussion gathered. Audrey continues the discussion in So Now What, asking for positive suggestions to improve the situation.

  • Rack 1.0, a modular Ruby webserver interface - It's shipped. Upgrade with caution, though, as there are early indications that it may not play well with Rails 2.3 release version in some places.

  • Rails Devs for Data Integrity: How to gracefully handle database key violations Not every Rails developer ignores the database layer.

  • Phusion Passenger 2.2.2 released - Instant Rack 1.0 compatibility.

  • Why Rails is Still a Ghetto - Another take on the flap over the "CouchDB: Perform Like a Pr0n Star" talk.
  • Reader Comments

    There are no comments for this journal entry. To create a new comment, use the form below.

    PostPost a New Comment

    Enter your information below to add a new comment.

    My response is on my own website »
    Author Email (optional):
    Author URL (optional):
    Post:
     
    Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>