Why Your Engineering Team Is Slow (It's the Codebase, Not the People)
A two-minute interactive audit to score whether technical debt is dragging your engineering team. Five signals that separate people problems from code problems.
Posts tagged: development
-
-
How to Close a Tab in Vim
To close a tab in vim, use :tabclose
-
How I Audit a Legacy Rails Codebase in the First Week
My Rails codebase audit process: stakeholder interviews before code, Gemfile and schema before any tools, and a single-page triage as the deliverable.
-
How to Open a New Tab in Vim
To open a new tab in vim, use :tabnew
-
Rails default_scope: Why You Should Never Use It
`default_scope` quietly breaks `Model.all`, corrupts scope chaining, bleeds into associations, and can leak data in multi-tenant apps. Here's why it's dangerous and what to use instead.
-
Solved: Warning: Using the last argument as keyword parameters is deprecated
Ruby 2.7 deprecated the use of hashes in the last argument of a method call. Fix this warning by removing the curly braces or adding a hash splat (**) to a variable argument.
-
Vim: How to Open Current Opened File in New Tab
In vim, you can open the current file in a new tab by utilizing :tabnew %.
-
Rails: How to Use Greater Than/Less Than in Active Record where Statements
When querying ActiveRecord for greater than and less than, most people turn to including raw SQL in their codebase... But raw SQL isn't required!
-
Using Let and Context to Modularize RSpec Tests
When test suites contain a lot of duplication, coupling occurs at an individual spec basis. By utilizing core RSpec functionality, developers can clean up specs in order to reduce duplication and add clarity to the focal point of the spec.
-
What's the difference between a Good Developer and a Good Googler?