Things I've written down.
Ruby, Rails, performance, security and applied machine learning. Updated when something feels finished.
Your dependencies are your attack surface
A modest Rails app pulls in a hundred-odd gems and several hundred transitive ones. Almost none were chosen by anyone.
The 55% page-load win was four queries and a cache key
Cutting clinical-study page loads by more than half under real traffic. Not a rewrite — profiling, eager loading, and one honest look at what was cacheable.
Chunking is a retrieval decision, not preprocessing
How you split documents determines what is findable. Everything downstream inherits that choice, and almost nobody measures it.
Everything that runs before your controller
A Rails request passes through twenty-odd middleware before your code sees it. Knowing the stack turns a class of mystery into a list.
Where SQL injection still lives in Rails
Active Record parameterises almost everything. The gaps are specific, well known, and exactly where people write raw fragments.
Your model didn't degrade, the world did
Model weights are frozen the day you deploy. Everything they were fitted to keeps moving, and nothing tells you unless you look.
Time zones: store UTC, and know which "now" you called
Most time-zone bugs come from two nearly identical methods and one place where dates are not really times.
Rate limiting the endpoints that actually get abused
Blanket limits annoy real users and barely inconvenience attackers. The endpoints worth protecting are a short, specific list.
The tests worth writing
Coverage measures which lines ran, not whether anything is verified. What actually catches regressions is narrower and cheaper than a coverage target.