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.

Object Oriented Ruby

I have been seeing a lot influence in ruby from Functional programming and not as such in ruby itself but in code written in ruby. Developers try new things, they are fascinated by other languages, how they solve problems. They try to change ruby into functional language, they loose sight of how problems can be solved in the Object Oriented Programming. Let’s do a refresher of some most important aspects of OOP. Read more on OORuby

Integrating Trailblazer and ActiveRecord transactions outside of a request lifecycle

When you use Ruby on Rails with ActiveRecord, you can get used to having separate transaction on each request. This is valid also when using Trailblazer (when inside of a request scope), however Trailblazer on its own does not provide such functionality. It means that when you’re using it from the console and/or when you process stuff inside background workers, you no longer have an active transaction wrapping around an operation. Here’s a blog post I wrote on how to add such functionality into your operations.

"Ruby Web Dev: The Other Way" guide

I have started my personal guide to give a junior/middle Ruby wed developers a brief insights on different aspects: from Ruby code architecture to Frontend and DevOps. All the things that I consider viable for a modern Ruby Web Developer. As soon as some topic appears in our team’s internal discussions, and it has pros/cons - it is transferred to this guide. [more inside]

Improving Large Rails Apps with Service Objects

Nothing has improved my Rails apps more than service objects. A couple of weeks ago, I was asked to help out with an established Rails app. I found a User model that included 28 modules. All but 8 were namespaced under Users. A core object in your system, used everywhere, and it’s thousands of lines long. Madness like this can be sidestepped with service objects. Find out how.

Loading older posts