ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #ruby
Learn how to use the frozen_string_literal pragma in Ruby to reduce memory allocations and improve GC performance while avoiding FrozenError crashes.
Stop duplicating tests for similar classes. Learn how to use RSpec shared examples to define behavioral contracts and keep your test suite DRY and maintainable.
Stop duplicating tests across similar classes. Learn how to use RSpec Shared Examples to define common behaviors once and apply them across your entire test suite.
Stop relying on opaque options hashes in Ruby. Learn how to use required and optional keyword arguments to create explicit, maintainable method signatures.
Learn how Ruby keyword arguments let you pass parameters by name, avoid ordering bugs, and keep method signatures stable as APIs grow.
Learn how to diagnose and resolve Errno::EMFILE (Too many open files) in Ruby by identifying file descriptor leaks using lsof and implementing safe file/socket handling to prevent crashes.
Learn how to use RSpec shared examples to eliminate redundant tests across similar classes, using it_behaves_like and include_examples for DRYer Ruby test suites.
Ensure that HTTPS requests made with Ruby's Net::HTTP succeed in production environments where the system may lack a trusted CA certificate bundle. Locally, the default OpenSSL store is usually present, so requests complete without error. In minimal containers or hardened servers, the bundle can be absent, leading to OpenSSL::SSL::SSLError: certificate verif
Deciding on a mocking strategy for a growing RSpec suite Our team is standardizing how we isolate collaborators in unit tests, and we keep hitting the same unresolved decision: when to use allow , when to use expect , and when spies are the better fit. The suite mixes all three styles inconsistently, and reviewers disagree on what each test is actually promi
rspec
openssl