Wrapbook Engineering

I wanted to give a quick overview on a simple method to illustrate some interesting StimulusJS and JavaScript concepts.

When displaying a lot of tabular data as we do at Wrapbook, it can become difficult to manage the individual columns that must render within the table. This can be because an addition or removal needs to be made, or because the rendering is driven by a feature flag.

How to write system tests for ViewComponents to ensure your Stimulus controllers behave correctly.

A nice expansion to the rails db:rollback command that allows engineers to quickly rollback changes specifically for the current branch.

It's not that easy to make an easy change. Especially if that change is applied to an existing large table.

Mind those callbacks when broadcasting live.

Major PostgreSQL version upgrades in AWS RDS are a pain. Here's what I wish I'd known about AWS DMS.

Feature flags are an effective method for developing and introducing large changes to an existing codebase without large interruptions to the engineering team. We have over 400 ERB files (views & partials) in our Rails app, and we re-wrote all of them over the course of 9 months using feature flags.

In a small team or a small codebase, upgrading from Ruby 2 to 3 is often a short and decisive process. However, at Wrapbook we have a large codebase split across six teams with over 50 people contributing daily. To put some meat to that, running rails stats on our majestic monolith returns over 180k lines of code.