Ruby on Rails is the world’s fastest web framework for startups

Past issues Subscribe

Feb 11 Mar 11

Feb 25 2021

Ruby on Rails is the world’s fastest web framework for startups

What is Ruby doing on Rails?

Hello, you're reading Infinum Ruby Drops, bringing you the latest Ruby and Rails related news straight to your inbox every week.

Ruby on Rails is the world’s fastest web framework for startups

As an entrepreneur, my definition of “speed” is “the amount of time and money it takes to reach an objective”. Code execution speed sometimes matters, because I want happy users. But once the app is fast enough, being faster doesn’t help much. Fast means “fast enough to get the job done”.

Rails

Rails design patterns - the big picture

This article is a high-level overview of design patterns that are commonly used in Ruby on Rails applications.

Using Webpacker in Your Ruby on Rails Application — a Deep Dive

Let's take a deep dive into Webpacker and see how the tool works under the hood.

Ruby

Simplifying Tests by Extracting Side-Effects

Test-driven development, object-oriented design, and functional programming converge on some similar ideas.

Ruby's not keyword is not not but ! (not)

The title is confusing enough, so I don't want to bore you you with words today, let's better listen to some deep-sounding Rspec code..

Blast from the past

MonolithFirst - Martin Fowler

Going directly to a microservices architecture is risky, so consider building a monolithic system first. Split to microservices when, and if, you need it.

How can you not be romantic about programming?

This world of programming is held together by code. Millions and millions of lines of code. Nobody knows how much there is. Some of it is more than 30 years old, some less than a week, and chances are you used parts of both yesterday.

Beyond Ruby

How much is your fear of continuous deployment costing you?

Most people aren’t doing true CI/CD. Most teams wait far too long to get their code into prod after writing it. Most painful of all are the teams who have done all the hard parts — wired up continuous integration, achieved test coverage, etc — but still deploy by hand, thus depriving themselves of the payoff for their hard work.