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.

Popularizing your Ruby gem

Once you’ve published your own ruby gem, learn what to do next to get the most out of it. Promote your ruby gem and engage with the developers in the Ruby community [more inside]

How to neatly organise assets in a Rails app

Rails comes packed with a lot of useful conventions. However, it doesn’t say much about how we should organise our front end assets. Here is a way in which we can leverage the same conventions we use to organise our controllers and views to have a neatly organised assets directory. [more inside]

Using reCAPTCHA v3 with Turbolinks

reCAPTCHA v3 will stop working after a Turbolinks navigation. This implementation works by using the API’s explicit render (for the badge) and data-turbolinks-permanent to keep it on navigation. read more

What makes a great software engineer, great

Today I woke up wanting to start a discussion about what it takes to be an awesome software engineer. I constantly see recruiters evaluating candidates solely based on their programming skills. Hence, most developers focus only on learning the latest programming language out there. Is that all it takes? Here’s my two cents on the matter. [more inside]

RFS: Attr Reader, Writer and Accessor [free video]

In ruby a lot can be achieved in a single line of code. Defining our own getters and setters is usually done when we need custom behavior for all other cases there is already something built in ruby. We’ll cover attr_reader, attr_writer and attr_accessor in this post.

Fail Better: Turning Software Errors into Documentation

The open-source community has done a great job of promoting good documentation as a necessary trait for the success of a software project, whether it be a utility library, a larger framework or a standalone program. In my latest article I explain how we can take it one step further and also use error messages to educate our users.

Invalidating caches when using many-to-many associations in Rails

Implementing various methods of caching in Rails is relatively simple, and in most basic cases Rails handles cache invalidation out of the box or with minimal code. But when using many-to-many associations, propagating changes in one object to all its associated objects needs some setting up so that Rails can handle cache invalidation. In “Invalidating caches when using many-to-many associations in Rails,” I talk about various methods of achieving this, and why one should choose one over the other.

Run.rb (Ruby 2.6 compiled to WebAssembly)

My friend Will Glynn and I worked on a project recently that allows you to type out and execute Ruby code without ever leaving the browser. It’s Ruby 2.6.0 compiled to WebAssembly! We call it run.rb and pronounce it “runner bee.” Our next goal is to add the standard library to the website. Please give it a spin and let us know what you think! I wrote up a quick explanation of why I wanted to build it here. I’d love any ideas of how we can make it better. ❤️

Testing Rake tasks.

Some developers argue on the real value of testing Rake tasks since they’re only used once or on rare particular occasions. Others think it’s enough to extract all the logic out of them to properly tested objects (we’ll look into that later). Before fully diving into the question of how to test them (and if it’s really worth it), we’ll take a quick look at Rake tasks themselves. [more inside]

Video Tutorial: Unpacking a Vue.js and Rails app

What does it take to put together a modern single-page web app using Vue.js on the frontend and Rails as the backend API? The Pragmatic Studio unpacks the design, architecture, and implementation of a full-stack application so you understand how everything works together. No need to get bogged down in figuring out how to put all the pieces together yourself.

Loading older posts