Dev Patel
Artifact JAN – APR 2024Source

Quant A&M

A Rails application for a quantum computing club, built test-first and shipped through CI to 300+ members.

Classification
Artifact
Client
Texas A&M
Window
JAN 2024 → APR 2024
Duration
3 MO
Status
Shipped
The problem

The problem

The club was running membership, events and resources out of spreadsheets and group chats. It needed an actual application, and it needed to survive being handed to whoever ran the club next year.

What I built

What I built

Ruby on Rails with PostgreSQL, containerised with Docker so a new maintainer gets a working environment without a day of setup.

Test-first with RSpec — not because the domain was risky, but because the handover was. A suite that runs on every push is the only documentation that can't go stale.

GitHub Actions runs the tests and deploys to Heroku; project workflow tracked in Jira on an Agile cadence.

Measured

Measured

300+users
TDDRSpec throughout
CI/CDActions → Heroku
  • Reached 300+ users inside the club.
  • Full RSpec suite gating every deployment.
  • Containerised so onboarding a new maintainer is a clone and a compose command.
Plan

Plan

Plan

5 items · scale 1:1
MEMBERS300+1RAILS APPMVC2POSTGRESQLDocker-composed3GITHUB ACTIONSRSpec → deploy4HEROKUhosting5
Note · Nothing exotic — the value is that every box is reproducible by the next maintainer.
What I'd redraw

What I'd redraw

I wrote model tests thoroughly and request specs barely at all, so the suite caught logic errors and missed routing and permission mistakes — which were exactly the ones users hit.

Materials

Materials

Ruby on RailsPostgreSQLDockerRSpecGitHub ActionsHerokuJira