scarver2 TOOLBOX

TOOLBOX

Tools I actually use. Curated on purpose. (If it’s not here, it’s not a religion — it’s just not my current default.)

Pragmatic Production-first DX matters Ship & iterate

CORE STACK

Where I’m fastest and most effective.

Ruby / Rails

Rails architecture, upgrades, rescue missions, and greenfield builds with sane boundaries.

  • Rails, ActiveRecord, migrations, performance tuning
  • Hotwire / Turbo / Stimulus when it fits (not dogma)
  • Service objects, domain boundaries, maintainable patterns

Data & Queues

Reliable background processing and data workflows that don’t wake anyone up at 2am.

  • Postgres (indexes, query tuning, constraints)
  • Redis + Sidekiq / Solid Queue (job safety + visibility)
  • Idempotency, retries, dead-letter thinking

Delivery / Ops

Build pipelines and deploy flows teams can trust.

  • Docker, reverse proxies (NGINX/Traefik patterns)
  • CI/CD (GitHub Actions), versioning, release hygiene
  • Zero-drama deploys, health checks, rollback readiness

ENGINEERING PRACTICES

The stuff that makes software survivable.

Quality

  • RSpec / Minitest (right tool for the job)
  • System tests when it protects revenue
  • Linters + conventions as guardrails

Observability

  • Structured logs with intent
  • Metrics that map to outcomes
  • Tracing mindset for distributed systems

Architecture

  • Monolith-first, modular by default
  • Extract services only when it pays
  • Interfaces, contracts, and clear ownership

Leadership

  • Translate between execs and engineers
  • Decision logs, planning, and trade-off clarity
  • Mentoring and leveling up teams

IN THE LAB

Things I’m exploring (because curiosity is part of the job).

Typed Ruby

Sorbet-style patterns when they reduce ambiguity and raise confidence.

Performance

Profiling, queue throughput, and “make it fast without making it fragile.”

Developer Experience

Scaffolds, generators, and workflows that keep teams shipping.