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.

tty-prompt v0.22.0 release with many new features

The latest tty-prompt release packs many new features that further enhance prompting users for input. Conversion of input into Array or Hash objects, :quiet option to silence output and allow for dynamic menus, :show_help option to control help display (on_start/always/never), shortcuts for selecting of all/reverse choices in multi-select prompt and much more. Enjoy!

Building a Toy Lexer in Ruby

Lexers are magical. They take your messy, hand-typed, human text, and convert it into a clean data structure that the computer can process. Every time you run a ruby program, use structured search or type in a date by hand, you’ll find a lexer hard at work. In this article, Alex Braha Stoll pulls back the curtain to show us how lexers work and how to implement one for a simple programming language. https://www.honeybadger.io/blog/building-lexer-ruby/

Sharing Code with Ruby and Rails

Ruby and Rails provide many ways to share code between objects. If you’re new to Ruby or Rails, or don’t work in them often, it can be hard to remember what each one does. Despite this, each of these tools serves a different purpose in a Ruby system’s architecture; understanding when to choose one over another can make your code more readable and maintainable. [more inside]

Pragmatic Rails Testing

I’ve been writing tests for Rails apps for over 5 years. I’ve come to a conclusion that well-written test suite makes developer more productive in the long term. The idea is to strike an optimal balance between not testing at all and writing zillions of tests. But where is this sweet spot? [more inside]

Loading older posts