The Git Commands I Run Before Reading Any Code
Five git commands that tell you where a codebase hurts before you open a single file. Churn hotspots, bus factor, bug clusters, and crisis patterns.
Piechowski.io Development Blog
-
-
Ruby 3.2 Is EOL: What You Actually Need to Do
Ruby 3.2 hit end of life on March 31, 2026. Here's what that actually means for your Rails app, how to assess your real risk, and the fastest safe upgrade path, without the vendor panic.
-
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.
-
Rails 7.2 to 8.1 Upgrade: What Actually Breaks and How to Fix It
Everything that breaks upgrading Rails 7.2 to 8.1, and how to fix it: enum syntax, the Solid trifecta, Propshaft, params.expect, and every silent regression.
-
Migrating from Sprockets to Propshaft: Is It Worth It?
Rails 8 ships Propshaft by default, but migrating from Sprockets isn't always the right call. How to decide, and a step-by-step migration guide for when it is.
-
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: ActionController::ParameterMissing (param is missing or the value is empty)
When using Ruby on Rails' strong_params with require, there is a chance the key doesn't exist. When this happens, an ActionController::ParameterMissing exception is thrown.
