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 and iOS developer.


A Fresh Cup

Notes on Rails and other development


Double Shot #448

Rails 3 sounds potentially exciting. Now to watch for it to actually happen.

  • Stykz - Because everyone needs a free multi-platform stick figure animation program.

  • Railfrog - A long-dormant Rails CMS showing signs of coming back to life.

  • Breath fire over HTTP in Ruby with Typhoeus - New ruby library for parallel HTTP requests.

  • Thursday

    Double Shot #447

    Today needs to be about writing code.

  • Record Filter - A pure-ruby DSL to replace SQL in ActiveRecord. Personally, I'd be happy with more SQL, but to each their own.

  • on APIs: more craft, less magic - "Rails seems to assume that you want to expose your database object model transparently through your API. In my experience, this is rarely what you want to do. In fact, it is a crazy way to live."

  • A git-style wiki system - Bryan Thompson ponders a way to help Rails newbies with common questions.

  • Tuesday

    Double Shot #446

    Up early with sleepless children. Gonna be a fun day.

  • Spree 0.8.0 Released - Another milestone for this open source Rails commerce platform.

  • Maps, Geolocalization and Optimization with Maptimize - Some fun techniques for those of you doing mapping in Rails.

  • Boks - AIR application that gives you a visual designer to set up layouts for Blueprint CSS.

  • How-To: Rack Middleware for API Throttling - A more reasonable use case for Rack than some I've seen.

  • Dreaming of Rails as the Next Microsoft Access - As an ex-bigshot in the Access world, I understand the sentiment here, but...no. I approve of devs with hats though.

  • Liquibase - XML-based tool for handling database change management. Looks interesting, but hard to see how I'd integrate it with Rails development.

  • Inkscape - Open source scalable vector graphics editor. Spiffy.

  • lazy_developer - A bunch of rake tasks to make working with Rails easier, notably (for me at least) one to reverse-engineer the schema to clean migrations.

  • Monday

    Double Shot #445

    Life goes on after the very successful RailsBridge launch.

  • RubyTrends - See which projects, addins, books, and practices are popular in the community. Or at least the part of the community that votes.

  • The First Rule for Software Development - Keith Casey explains why it's "Don't Trust the Users."

  • Inochi 1.0.0 - A milestone for this gem builder with lots of bells and whistles.

  • honeypot - Simple honeypots to keep spammers away from your Rails forms.

  • Monday

    Announcing RailsBridge

    This morning, I'm pleased to be able to announce a new initiative that I've played a small part in launching: RailsBridge. The easiest way to explain the reasoning behind RailsBridge is to quote from the web site:

    The RailsBridge Mission:

    To create an inclusive and friendly Ruby on Rails community.

    The RailsBridge Guidelines:

    • First, do no harm. Then, help where you can.

    • Bridge the gap from aspiring developer to contributing community member, through mentoring, teaching, and writing.

    • Reach out to individuals and groups who are underrepresented in the community.

    • Collaborate with other groups with similar goals.

    RailsBridge is the product of intense discussions among 40 or so Rails and Ruby developers. We have quite a number of projects in the launching stage, from public Rails workshops to mentoring initiatives to some fun learning experiences for Ruby newcomers.

    But the key message of RailsBridge is simple, and goes beyond any one project: the Rails community is the product of everyone who participates, and it can be a positive force for good in the world. We think there are enough Rails developers who feel this way that the somewhat negative image of Rails that is current in some parts of the web can be revised - not by claiming that we're welcoming, but by actually acting that way.

    If you're already living in the Rails community that you want, great. But if recent events have convinced you that things could be improved, come join us! If we all work together to move things forward, then the awesome Rails codebase can be joined with an equally awesome community, and everyone wins. There's more information on the RailsBridge home page, or you can come join us on the RailsBridge Google Group to help build a better future.