Project-specific RuboCop rules can flag conventions and stop the pipeline with little code, such as banning TODO and WIP comments in Ruby files.

301 and 308 redirects can be cached by browsers indefinitely without cache control, making later changes impossible unless users clear their cache.

Date.parse guesses date formats and can accept invalid input, producing unexpected dates. Date.strptime validates against an explicit pattern and avoids ambiguous parsing.

Unsafe ActiveRecord query methods can expose applications to SQL injection when raw SQL is built from untrusted input.

Combining unknown CSS selectors safely fails when a selector list appears; :where() and :not() preserve correct matching without breaking lists.

Detecting when a CSS class is added can be done with a MutationObserver, useful for reacting to DOM state changes on selected elements.

Pinch-zoom, the on-screen keyboard, and other overlays can shift the actually visible page area beyond the layout viewport. VisualViewport exposes the visible region for positioning and tracking.

Start Terminator with split panes and predefined commands while keeping shells open after the command exits.

JavaScript value checks are inconsistent across primitives, objects, arrays, null, undefined, and NaN; the right test depends on whether you need type, instance, or property presence.

Rails uses configurable time zones, while Ruby time APIs follow the server zone and can return wrong results. Time.zone keeps date and time handling consistent.

Business-rule tests with multiple variables can explode into 2n permutations. An n+1 pattern keeps coverage manageable while making individual cases easier to follow.

Ruby local variables are visible after conditional branches, so a missing assignment can yield nil instead of an error and silently produce blank output.

String comparison can misorder gem and Ruby versions, letting newer releases slip past checks; Gem::Version gives reliable semantic version comparisons.

Complex Rails schema changes need SQL, embedded migration models, or adapter helpers when simple add_column and update calls cannot handle existing data safely.

Directory trees are easier to inspect with tree than repeated cd and ls, especially for nested structures. Depth limits and shell aliases keep output manageable.

Nested zero-delay timers are clamped by browsers, so repeated setTimeout(f, 0) calls can run several milliseconds late, especially in background tabs.

Slow Rails JSON endpoints often waste time in JBuilder, loading full records, and Ruby object allocation. pluck, database aggregation, and cached materialized views can cut response time dramatically.

RubyMine test file generation can produce excessive boilerplate, and file templates let you tailor the output to project needs.

Ruby method visibility differs from Java: private allows only implicit calls, while protected permits access between instances of the same class or subclasses.

Spreadsheet apps can interpret CSV cells beginning with =, +, -, or @ as formulas, turning exported user input into a security risk.

Custom icon fonts can render as garbled characters after switching from Sprockets to Webpack because CSS charset detection changes. Adding a UTF-8 BOM or an explicit charset can prevent intermittent display failures.

GraphQL APIs return nested data through one endpoint, and Ruby can query or mutate them with plain HTTP requests without adding graphql-client.

Rails npm packages need a version mapping from 4-part gem releases to npm’s 3-part semver, so package ranges keep working across patch and prerelease builds.

Format durations into the nearest human-readable unit with locale-aware pluralization using Intl.NumberFormat, defaulting to German.