Many voices. One Flagrant.
This is the second post in a series on things we explored while “Revamping the Ruby Central Conference Websites”. Lesson 1: Knowing When to Build vs Dig Lesson 2: Averting Monkey Patches with a Custom CMS ⬅︎ Lesson 3: Braving Mad Science with Tailwind Lesson 4: Planning...
Filters:
November 15, 2022
This is the second post in a series on things we explored while “Revamping the Ruby Central Conference Websites”. Lesson 1: Knowing When to Build vs Dig Lesson 2: Averting Monkey Patches with a Custom CMS ⬅︎ Lesson 3: Braving Mad Science with Tailwind Lesson 4: Planning
November 15, 2022
This is the first post in a multi-part series on things we explored while “Revamping the Ruby Central Conference Websites”. Lesson 1: Knowing When to Build vs Dig ⬅︎ Lesson 2: Averting Monkey Patches with a Custom CMS Lesson 3: Braving Mad Science with Tailwind Lesson 4:
August 30, 2022
Imagine you’re digging through some part of a system, and you come across something that looks confusing. You’re trying to figure out why something is done, or why it’s done the way it is. You have so many questions running through your head: Was this a conscious decision? Did it just happen?
February 28, 2022
I recently had the pleasure of refactoring a view file for a client project. The pleasure part of that sentence is a lie and definitely laced with sarcasm. I grew more grey hairs and thought of throwing my computer out the window several times. via GIPHY So why was it so damn difficult to
February 15, 2022
What a sad situation. A lonely child record has a foreign key that points to a parent record of a primary key that no longer exists. Sob How could we, as software developers, let this happen? Imagine we have three tables: dogs, walkers, and a join table that is called dog_walkers. Great,
January 27, 2022
Have you heard of a “design pattern”? If you have, and if you know the history, and if you don’t feel like double- or triple-checking how well I’m going to explain this, you can skip this entire post. Otherwise, buckle up! Simply put, a “design pattern” is a general, reusable solution to a
November 12, 2021
When tasked with figuring out why unexpected behavior was happening in our app, I followed the bread crumb trail to this block of code: def trial_days Arel::Nodes::Multiplication.new( Arel::Nodes::NamedFunction.new('COALESCE',[arel_table[:trial_days], TRIAL_DAYS]),
October 27, 2021
Look at you. You learned so much about software, that the intelligent folks at Flagrant HQ decided that you were capable of learning A LOT more about software. Way to go, I’m sure that was difficult. You deserve a pat on the back, a firm hand-shake, heck i’d even buy you a slice. So you ‘git’
September 23, 2021
Pagination With Hotwire In the pantheon of classic user stories over the years of modern web development, pagination is certainly well represented. The first release of the long lived will_paginate gem goes all the way back to 2008 and the early years of Rails. Amazingly, newer gems like
March 19, 2021
We have been building a Responsive Web Chat application. In order to provide users with a look and feel similar to a native app we decided to include page transition animations using the CSS and Javascript frameworks in our application, TailwindCSS and StimulusReflex. At the same time a visual
February 2, 2021
Comparing StimulusReflex and Hotwire Over the past few posts we’ve been talking about Reactive Rails and our experiences with Hotwire and StimulusReflex. If you’d like some detail, you can catch up: Reactive Rails In Context Reactive Rails From Bare Bones Reactive Rails:
February 2, 2021
A Brief Study of Hotwire We continue our exploration of Reactive Rails tools with Hotwire. This is the fourth post in the series–if you need to catch up, you can: Reactive Rails In Context Reactive Rails From Bare Bones Reactive Rails: StimulusReflex Reactive Rails: Hotwire
February 2, 2021
A Brief Study of StimulusReflex This post continues our exploration of Reactive Rails tools with StimulusReflex(SR) and its underlying libraries CableReady(CR) and Stimulus. This is the third post in the series–if you need to catch up you can: Reactive Rails In Context Reactive
February 2, 2021
Reactive Rails: Bare Bones Chat Introduction This is the second article in a five-part series on Reactive Rails. In the first post we wrote a brief primer noting the history that brought us to these notions of Reactive Rails. In this post, we’ll build the barest of applications–a base from
February 2, 2021
Reactive Rails In Context At Flagrant, we recently began designing a chat-centered product. As we were reaching for React, Basecamp dropped hotwire. This gave us pause–by and large, React includes a lot of overhead, and some members of the team make an unpleasant face when React gets
