Here’s a practical map of what I reach for most often — not an exhaustive résumé keyword list.
| Area | Tools |
|---|---|
| Languages & frameworks | Ruby on Rails, React, TypeScript, JavaScript; Python for scripts and ETL |
| Data | PostgreSQL, MySQL, MongoDB; Redis; Apache Solr for search |
| Async & caching | Sidekiq, Solid Queue, Solid Cache |
| Frontend state | Redux, Redux-Saga |
| Testing & CI | RSpec, GitHub Actions, Jenkins |
| Infra & deploy | Docker, Ansible, Capistrano; Nginx, Puma; DigitalOcean |
| Observability | New Relic, Monit, logrotate |
I pick tools to match the problem: Rails for fast, maintainable backends; React when the UI needs rich client state; Python when pulling and cleaning data from CSVs or databases is faster than doing it in Ruby.
This site and my interactive CV are examples of the React + TypeScript side; most of my day jobs have been Rails-first with a React or legacy JS frontend.
Public comments are closed, but I love hearing from readers. Feel free to contact me with your thoughts.