Developing with Browser Guards in Rails 8
Rails browser guards are useful until your own mobile emulator gets blocked by the default modern-browser rules.
Rob Zolkos
Building Software. Lots of AI lately. Curious and creative. Sharing what I learn.
You can find me on Twitter, GitHub, or write me an email
Rails browser guards are useful until your own mobile emulator gets blocked by the default modern-browser rules.
A Rails 7.1 upgrade quadrupled Heroku memory because Puma quietly started using every reported core.
Production-only Action Mailbox failures are easier to fix when you replay the raw email locally and reroute the broken ones.
The tiny command-line incantation that gets Ruby 2.6.7 compiling on macOS Big Sur with asdf.
Chrome DevTools can catch the exact JavaScript line that secretly mutates your DOM.
Rails runs `after_commit` and `after_rollback` callbacks in reverse order, which is exactly the kind of detail that bites later.
A stubborn bug became a lesson in pairing, documentation, onboarding, and why pride is expensive.
One broken IE7 login proved the hard way that your test suite is only as good as your knowledge of real customers.