ruby
72 stories and discussions about ruby, aggregated from every source we track.
DHH's opening keynote had shockingly little to say about Rails.
I mentioned in my Hello, world! post that I built this site using Hanami. This site may seem simple on the surface; it is, after all, just a blog. However, the backend is packed with features that help me day to day. I…
<p><strong>TL;DR: Should I give a "time out" to 'newbies' who have been 'newbies' for (subjectively) too long, or am I being too harsh?</strong></p> <p>Let me start with a graph.</p> <p><a href="https://raw.github.com/gist/9e8f8b837c1eb7e68c90/6332a8a13e51ae71adf2cdfad04d8dbb1839f791/skill-vs-time.png" rel="ugc">https://raw.github.com/gist/9e8f8b837c1eb7e68c90/6332a8a13e51ae71adf2cdfad04d8dbb1839f791/skill-vs-time.png</a></p> <p>Now let me explain what the graph <em>means</em>.</p> <p>The red and yellow lines in this graph are two people who have been in the Ruby on Rails community <em>about</em> the same period of time. The person represented by the red line has gained more skill over a shorter period of time than the person represented by the yellow line. Let's say the total time for this graph is 18 months. Both people, for all intents and purposes of this story, are gainfully employed as Ruby on Rails developers. Where they work, what they are paid and what they're building aren't important to this story. What is important is the role that these two people play in the #rubyonrails channel on Freenode.</p> <p>Yellow is in the channel nearly every single day continuously asking questions. Red (not me, by the way) is there, again, nearly every day, answering questions from people like Yellow. Occasionally, these questions take anywhere from mere seconds all the way up to (in more than one case) <em>5 hours</em> to answer. These questions are usually relatively simple things, like defining custom validations, working out nested resources or figuring out syntax errors in ERB code.</p> <p>Now, I don't personally have a problem with people who take up the channel's time by asking question after question after question, month after month after month. That's what the channel's there for. If we didn't allow all those questions then why even have the channel in the first place? My problem is that I think that a lot of the answers to these problems can be solved in a better way than asking anonymous strangers on the internet for help. Like reading <a href="https://railstutorial.org" rel="ugc">free</a> and <a href="http://manning.com/bigg2" rel="ugc">not so free</a> about the topic, for instance. Or finding an anonymous stranger who can consistently volunteer their time to help build the thing that they're having issues with, and become not-so-anonymous, perhaps even a friend.</p> <p>Basically, IRC is a shitty medium for discussing big programming architecture problems, but a great one for teeny-tiny problems.</p> <p>In IRC-land, Red only has so much patience to help Yellow in their quest for learning. If it appears that after a long time that Yellow isn't actually learning anything from what they've been told and they aren't applying any actual critical thinking to the problem space, then Red may get annoyed at the "slow-goingness" of the progress. I've seen this happen. Hell, I've been annoyed myself that some people just don't 'get it' sometimes. But what I realised is that, as the above graph shows, different people learn at different speeds. As an extension of that, different people learn better from different resources. Some people may learn better from just brute-forcing a problem. Others may need hand-holding and a walkthrough of the problem several times before they finally understand.</p> <p>I don't know what the "correct" answer is to this problem. Do you maintain the status quo and let Yellow keep asking questions, day in and day out and hope that, over time, there is actually something to show for it; that they actually reach a higher form of competency? Or do you encourage them (perhaps forcefully so) to look into other means of improving their knowledge in the field? I just don't know.</p> <p>WDYT, Lobsters?</p>
Packwerk is an open source static analysis tool used to enforce boundaries between groups of Ruby files we call packages.
With Rust, you can do low-level number-crunching and bit-by-bit processing, while enjoying memory safety and concurrency features. With Helix, you can use your Rust code inside of a Rails project.
Update (2023-06-28): Added “I required a file, but I want to know what files were actually loaded” I love puts debugging I am a puts debuggerer. I don’t say this to disparage people that use a Real Debugger. I think…
We are pleased to announce the release of Ruby 3.0.0-preview1.
Personal blog of Penelope, about, Ruby, programming, agile, and many other things
As an experiment to see how static typing could help improve our team’s Ruby experience, we introduced Sorbet into a greenfield codebase with a team of...
Something I must confess is that I absolutely hate writing these blog posts. It’s not quite as bad as having to give a conference talk, but it’s up there on the list of activities that feel like pulling teeth to me.…
Ruby's standard library is divided into default and bundled gems
Recently at work I was tasked with finding a memory leak in a legacy Ruby application I was unfamiliar with. We had been monitoring the application …
Today we’re going to discuss a couple of really simple numeric predicates - namely Numeric#zero? and Numeric#nonzero?. I assume most Ruby developers are familiar with them, as they represent a popular alternative to…
A tour of Hanami's foundational abstractions, dependency injection, providers, types, and contracts, with an honest look at the rough edges of each.
Modules are incredibly flexible and powerful constructs that help you organize your code in a more… modular way. They let you package related functionality i...
MRI Ruby's Global VM Lock: frequently mislabeled, misunderstood and maligned. Does the GVL mean that Ruby has no concurrency story or CaN'T sCaLe? To understand completely, we have to dig through R...
<p>Hey, I wrote this post for Engine Yard on trying to add a list comprehension syntax to Ruby.</p>
At some point in growing a large-scale software system, you’ll require “out of band” context: data which is not explicitly passed as an argument to a function but rather implicitly attached to the request, job or event…
:zap: From finding text to search and replace, from sorting to beautifying text and more :art: - learnbyexample/Command-line-text-processing
The 2026 Ruby on Rails Community Survey is now open. Add your voice to the community data. Brought to you by Planet Argon.
Learn Ruby metaprogramming: call methods dynamically with send, define them at runtime with define_method, and handle missing calls with method_missing.
How Ruby and Hypermedia can simplify the way we write API clients.
You’ve got an app with runaway memory use, what do you do hotshot? What do you do? If you’ve exausted the usual suspects it might be time to take drastic ste...
This blog post describes a design pattern for ensuring you consider every attribute in certain situations. I'll use Ruby on Rails in the examples, but the general pattern should apply to any language...
Ruby on Rails adalah framework web sumber terbuka berbasis Ruby, membantu pengembang berbagi pengetahuan, pengalaman, dan perkembangan terbaru dalam pengembangan perangkat lunak.
Contribute to nicolasva/solid-jobs development by creating an account on GitHub.
First-party Google Search Console and technical SEO engine. Automate Googlebot indexing, audit Core Web Vitals, and capture Google AI Overviews in pure Ruby with zero dependencies. - ApollosWave/gs...
Makes S1-model 'measurement' (and the collapse that follows it) a Ruby primitive. - innocentdiaz/s1_ruby
The following is a longtime favorite guest post by Flatiron alum Kevin McNamee, a software engineer at Casper. When mapping associations between models in your Rails application, you will inevitably come to a point…
Learn how to easily upgrade from capybara-webkit to Headless Chrome and ChromeDriver, the best tools to get tests done in Ruby on Rails projects.
Mobility has a new backend for storing all your i18n model data in a single json or jsonb column.