#rails
Qualified.at Is Live: When You Over-Engineer a Form, the Least You Can Do is Launch the Damn Site...
The three-gems + one npmjs package form engine from my SF Ruby talk grew a SaaS site with a pricing page. Qualified.at gives you tools to create multi-branching forms, extract answers from free-form text using LLM, and ultimately it qualifies your leads while you sleep, and, importantly, refuses to store anybody's SSN. Come poke at it, hopefully you'll like it. Up to 1000 leads is free forever.
Yes! It's 2021, and Ruby 3.0, and Ruby on Rails 6.1 are alive and thriving. Are you?
Weighing velocity, scalability, maintainability, staffing, and community against what Rails actually delivers in 2021 — with HEY's stack as a case study — to answer whether Rails is still the right choice, or just the comfortable one.
Detangling Business Logic in Rails Apps with PORO Events and Observers
With any Rails app that evolves along with substantial user growth and active feature development, pretty soon a moment comes when there appears to be a decent amount of tangled logic, AKA technical debt.
The Case For Vertical Sharding
In this post I share the story of overcoming a massive scalability bottleneck from too many writes ino the Analytics database table used for Event collection, using Vertical Sharding.
The Big Switch How We Rebuilt Wanelo From Scratch And Lived To Tell About It
In this post we share the details of what we did and what we learned, in case someone out there ever finds themselves in a similar situation, weighing the risks of either working with a legacy stack or going full steam ahead with a rewrite.