– It took about a month to get the MVP out and a few months after for it to be sellable

– Motivation for using Rails

– How the app works and going over some of its screens

– ActiveJob is such a good abstraction it’s easy to forget what job library you use

– A bunch of useful gems that are being used

– The user experience can often impact the technical complexity of what you’re building

– Feature flags and swinging back to JSONB columns

– Stripe handles all of the payments

– The app is pretty much one big monolith and it’s a good thing

– About 25k lines of Ruby code and 40k lines of Typescript on the front-end

– If Turbo were around for years would you have used it over React?

– You shouldn’t be afraid to touch code in your codebase

– Getting a decent amount of things planned out before implementing the code

– Postgres, Redis, Mixpanel and Datadog for app and business alerts / logging

– Limiting access to production data from developers

– Heroku helped them get to market faster and they had YCombinator credits

– The deploy process from development to production

– Limiting access at the GitHub repo level and Heroku

– In general backups are handled by the providers they use (Heroku, S3, etc.)

– Heroku will send out alerts if something unexpected is happening with the site

– Best tips? Be pragmatic about testing and code coverage

– User design and UX is handled by a specific team member

– Check out https://greatquestion.co and they’re hiring too