Fullstack Ruby

Back in the mists of time, I used a tool called rvm.

A new extension to Minitest Expectations by yours truly is the perfect illustration for this philosophy of programming. ➡️ TL;DR: a look at the code / examples A shorthand for how I think about the design of new APIs, whether I’m working on the Bridgetown…

Assuming you haven’t been living under a rock these past few weeks, the Ruby community has been embroiled in quite a bit of drama.

Well my Ruby friends, a new day has dawned with the release of the Ruby web framework Bridgetown 2, and that means I can start to enjoy the fruits of our labor by sharing useful code examples and architectural explanations here on Fullstack Ruby.

I always hate writing posts like this, which is why I rarely do it and tend to let content destinations linger on the interwebs indefinitely.

It sure seems like the Hanami web framework has been in the news lately, most notably the announcement that Mike Perham of Sidekiq fame has provided a $10,000 grant to Hanami to keep building off the success of version 2.2.

This is a right humdinger of an episode of Fullstack Ruby!

I don’t know about you, but after a while, I just get tired of the same arguments.

As the lead maintainer of the Bridgetown web framework, I get to work on interesting (and sometimes very thorny!)

It’s tempting to want to take the simplistic approach of writing “to the framework” or to the external API directly in the places where you need to interface with those resources, but it’s sometimes a much better approach to create your own abstraction la…