Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Lol DBA
lol_dba is a small package of rake tasks that scan your application models and displays a list of columns that probably should be indexed. Also, it can generate .sql migration scripts.
-
SimpleCov
Code coverage for Ruby with a powerful configuration library and automatic merging of coverage across test suites
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
gem "rubocop" - https://github.com/rubocop/rubocop | Set up code guidelines for your dev team, I recommend using whatever Standard recommends.
gem "rubocop" - https://github.com/rubocop/rubocop | Set up code guidelines for your dev team, I recommend using whatever Standard recommends.
gem "annotate" - https://github.com/ctran/annotate_models | Adds DB-schema comments to models. May be unnecessary on RubyMine, YMMW.
gem "lol_dba" - https://github.com/plentz/lol_dba | Inspect the state of table indexes.
gem "simplecov" - https://github.com/simplecov-ruby/simplecov | Gather spec coverage stats locally and on CI, aim for those 90+%.
gem "strong_migrations" - https://github.com/ankane/strong_migrations | Helps devs write non-blocking migrations, a must-have.
gem "packwerk" - https://github.com/Shopify/packwerk | Allows modularising Ruby code, a must-have for growing projects.
gem "test-prof" - https://github.com/test-prof/test-prof | Toolkit for inspecting and optimising your test-suite, a must-have.
Related posts
- Uniqueness validation does not work since the beginning of Ruby on Rails.
- Database Views & Rails Active Record: defining new Model classes out of views
- Evaluating More Coverage in Ruby 3.2
- Materialised views for serious performance gains
- Most performant way to build an analytics dashboard from a relational database backend that only stores numeric values, where the data the end-user sees is "categorized" into numeric brackets (e.g. 60-79 = Med, 80-100 = High, etc)