Hey everyone! Quick question for the Ruby folks here — what’s your IDE or editor of choice for day-to-day Ruby/Rails work? Do you swear by RubyMine? Live inside VS Code with a handful of extensions? Or are you one of the brave souls still hacking a...

I’ve been through a long parade of editors and IDEs over the years, and each phase almost feels like a snapshot of where I was as a developer at the time. Back at university the big names were NetBeans and Eclipse—heavy, clunky, but they got the job ...

Hey everyone! Thought we’d kick things off with some introductions. What’s your experience been like working with Ruby or Rails so far? Are you deep in a legacy app, or running shiny Rails 8 with all the trimmings? I’ll start: I’ve been working wi...

While grinding through the monumental JuggleBee upgrade, one of the recurring debates was: what do we modernize, and what do we leave the heck alone? Plenty got a shiny new coat of paint see my earlier posts for all the juicy details, but one area I ...

After having followed the various conventions defined by our Githttps://brazenbraden.com/posts/gitconventions/ and GitHubhttps://brazenbraden.com/posts/githubprocess/ processes, we should now be in a good place to take the code that has been produced...

My previous post on GIT Conventionshttps://brazenbraden.com/posts/gitconventions/ broke down various conventions around branching and committing code. As part of building a solid process around development, the next area to deal with is that of getti...

Hey everyone. Welcome to our brand-new Ruby & Rails group! This is a space for anyone working with Ruby — whether you’re wrangling ActiveRecord callbacks, crafting APIs, or pushing the edges of what Rails can do in 2025. The goal here is simple: sh...

Over the last decade or so, I have had the opportunity to experiment with various git usage strategies and styles. Ranging from branch names, to pull request descriptions, a lot of time has been spent thinking about how to best describe our work to c...

Feature flags are a way of life when developing software. They let you deploy code to production without immediately exposing it to users — like flipping a switch without blowing the fuse. In practice, they're used to: Ship features incrementally ...

Sidekiqhttps://github.com/sidekiq/sidekiq is pretty much the go-to solution for enqueuing jobs for background processing when working on a Ruby-based project. It's simple to implement, has a clear DSL, and is well-supported by common testing framewor...

Now that we had a deployable app, I set up a staging server using my new favourite provider, Hetznerhttps://www.hetzner.com/ not a sponsor, lol, spun it up, and witnessed a “fully functional” skeleton of JuggleBee. Stage 1 of the migration plan was c...

JuggleBeehttp://www.jugglebee.com was born in 2015. It was Namibia's first online auction platform and is still one of the biggest today. I built it with Ruby on Rails 4.2 on Ruby 2.2. It sat there, rock-solid and stubbornly stable, only needing the ...