After a few years of building side projects, I've settled into a stack I actually enjoy: Rails for the boring parts (auth, jobs, database), TypeScript for the interactive bits.
The pattern that works for me:
- Rails handles users, sessions, and background jobs
- A small TypeScript app for the parts users touch a lot
- One Postgres database, one deploy
It's not fashionable, but it ships. And when something breaks at 2am, I can read the stack trace.
I'm learning Rust now for a CLI I use in my workflow. Everything is a tradeoff, and I like having a few boring tools in the drawer.
Top comments (2)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.