Pinned
Thank you @shl
After our layoffs in 2015, the team at @BigBinary stepped in and helped Gumroad stay in business. We continue to work with them today. If you’re looking for a ruby/rails-focused dev shop, they have my full endorsement!
BigBinary
@BigBinary
BigBinary is exclusively focused on Ruby on Rails consulting. For over 14 years, we’ve built applications with Ruby on Rails.
- Debugging production frontend crashes is rarely straightforward. In this post, we walk through a real issue where the browser console pointed us in the wrong direction, while the actual problem was a circular dependency exposed by production bundling. We also covered why
- Debugging a bug that developers can't reproduce is a special type of fun. Recently, a few Neeto customers started reporting painfully slow page loads and sometimes pages wouldn’t load at all. The flow is simple. Browser -> Cloudflare -> Cloudfront -> origin. Finding the root
- Playwright traces are like flight recorders for your tests - they capture every action, network request, DOM snapshot, and console log during test execution. When a test fails, especially in CI environments, traces become the most powerful debugging tool, providing a complete
- We upgraded our Rails application from 7.1.5.2 to Rails 7.2.1.1, and we started getting StackOverflow issues. To identify the issue we had to take a deep look into ActiveRecord to understand how Rails handles 233 "OR" conditions and what exactly changed in between the two
