RubyFlow The Ruby and Rails community linklog

×

The Ruby and Rails community linklog

Made a library? Written a blog post? Found a useful tutorial? Share it with the Ruby community here or just enjoy what everyone else has found!

Submit a post

You can use basic HTML markup (e.g. <a>) or Markdown.
Note that your post may be edited to suit the format of the site.

As you are not logged in, you will be
directed via GitHub to signup or sign in

Post Preview

Note: Only the first pargraph is shown on the front page and overly long paragraphs may be broken up.

Testing your JavaScript... with Ruby?!

While Codest is primarily a Ruby shop, one of the many projects we’re building is in JavaScript. It’s a client-side library which runs in a pretty challenging environment: it has to support pretty much every browser in existence, including very old ones, and to top it off it interacts with a gaggle of external scripts and services. It’s tons of fun… read more here

Best of Practicing Ruby (Book Edition) by Gregory Brown et al @ Yuki & Moto Press

Hello, I put together a new (free online) book titled Best of Practicing Ruby (Book Edition) @ the Yuki & Moto Press Bookshelf that collects the best articles from the practicing ruby series headed by Gregory Brown with guest chapters by Luke Francl, Magnus Holm, Aaron Patterson, Solomon White and others. Topics include: A minimal HTTP server - Event loops demystified - Parsing JSON the hard way - Tricks for working with text and files - Working with binary file formats - and much more. Happy hacking. Happy reading. Cheers.

Updated I Love Ruby

Hello People, have updated my Ruby book I Love ruby. Its a minor update where online resource section was updated. Please grab it here https://mindaslab.github.io/I-Love-Ruby/

Hello from a fellow Ruby programmer, I have somehow stumbled on the last page o…
Any interest in publishing your manuscripts sources in markdown (on github)? P…

Build your own Ruby on Rails validations and use them like the default ones

Sometimes built in validations are not enough so we have to write our own validation rules. Because of this, our models can become fat really quick so the best idea to avoid it is to extract validation logic to separated classes. Such approach makes the code more clean, isolated and reusable - http://pdabrowski.com/blog/ruby-on-rails/validations/building-custom-validator/

Loading older posts