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.

CanCanCan 2.0 is out!

After few months CanCanCan has finally a new major version: 2.0. There are many important changes in the new version but very few new features. We thought it was time to bring the project back on track and drop support for a lot of unnecessary features. [more inside]

Podcast: Michael Feathers on Avoiding Legacy Code

What makes a code base go bad and become “Legacy Code”? Can teams avoid writing bad code? Michael Feathers, author of Working Effectively With Legacy Code joins Tech Done Right to talk about technical debt, how communication can prevent bad coding practices, why coding problems are never just about code, and what it’s like to go around the world seeing the worst code messes ever written. [more inside]

Fighting the Hydra of N+1 queries

A huge insight into the problem of N+1 queries with Rails: starting from the junior-level stuff (what is it and how to fight it) moving to the usage of bullet gem, hardcore problems caused by the complexity of the application and DRY/OO patterns used — and ramblings on how to tackle the problem at its root. [more inside]

Nice article!

Testing a Feature with Rails and RSpec: A deep dive

One of the things I hear most from developers who are new to Ruby and Rails, or just to testing is, How do you get started? What should I test? The value of testing your code and the confidence it brings is already apparent, but how to make it happen seems to be missing. In this post I address how I approach testing a fairly simple, but non trivial feature from start to finish. https://chrisherring.co/posts/testing-a-feature-with-rails-and-rspec-a-deep-dive

One more article about ruby best practice

Everyone engineer should read tech literature in free time. When you are reading you learn a lot of new things. You read about someone’s experience, best practice and fails. With that useful information you can see new opportunity, can make your code better and more stable, can create new features better and faster. In this article I want to share some good practice that I have read in tech literature. [more inside]

A better "bundle update"

If bundle update for your Rails projects is a risky a frustrating process, try bundleup instead! I wrote bundleup to use the same Bundler commands behind the scenes, but added some nice enhancements. My favorite feature is how it color-codes the gems that will be upgraded according to semver, so you can immediately spot the minor (yellow) and major (red) version changes that might cause your app to break. Install it with gem install bundleup and check out the documentation on GitHub!

Nice! Will try tomorrow (I do bundle update every morning)

Ruby: How a Language Reflects its People

https://pusher.com/sessions/meetup/sheffield-ruby-user-group/ruby-how-a-language-reflects-its-people What are the values that entered into the language by way of its core committers and what are the values we identify with as a community? How can making these values explicit help us foster a better community? What might Ruby be like if its community were primarily French, German, Italian rather than English-speaking and Japanese?

Loading older posts