Why Stanquette

I do not hand over a deck of recommendations and leave — I architect the solution and build it, with your team. Mentorship is built into the work: the team ends stronger than I found it.

House rules

Less tech is better. Rails is a prime engine for having less technology over more. Do you really need three data stores and twenty services — and how many people do you have to maintain them?

Merging services back together is fine. Microservices are great when investor money is ample. When the market tightens, rebundling into a monolith is just as valid as the original extraction.

I do not need to redo a system to fix it. Coming from a long career in film, I know that deadlines and budget constraints got you where you are. Your app did its job — it deserves respect, not scolding.

Rails is great for LLMs. Terse code means less to ingest. I structure libraries and documentation so a model is productive from the very first prompt.

Recent work

A good fit if…

  • You are open to having decision-makers work directly with me
  • You want everything out of the Ruby/Rails stack you already run on
  • …or you are starting a new initiative with a lean Ruby-based setup
  • You are open to forms of collaboration other than full-time employment

Technical expertise

Focus

  • High-performance web applications and APIs
  • Lightweight frontend architecture (it doesn't always require React)
  • Database optimization and data processing
  • Background jobs and distributed computing
  • File processing and streaming systems

Ecosystems

  • Ruby with and without Rails (20+ years)
  • JavaScript, Go, Crystal
  • GCP and AWS: queues, databases, VMs