🎱 Josh Branchaud ✨
banner
jbranchaud.bsky.social
🎱 Josh Branchaud ✨
@jbranchaud.bsky.social
Free-Range Software Dev and Consultant ✨ PostgreSQL • Ruby on Rails • TypeScript • React ✨ 🏃🐈🍹🎱 (he/him) | Chicago | Work with me: visualmode.dev
Definitely not good at Chess 😅 but I do have a lot of fun with the puzzles
November 25, 2025 at 2:07 AM
Here is the script in case you're curious github.com/jbranchaud/d...
github.com
November 24, 2025 at 11:19 PM
Sharing this internally, gonna see if I can get you a sale or two 🙌
November 20, 2025 at 4:34 PM
yes, I was about to add this to the thread as a Rails-specific option!
November 20, 2025 at 4:25 PM
The "Don't Do This" page from the PostgreSQL wiki is usually good as a conversation starter for potential pitfalls.

wiki.postgresql.org/wiki/Don't_D...
Don't Do This - PostgreSQL wiki
wiki.postgresql.org
November 20, 2025 at 4:11 PM
I also like to point to the `strong_migrations` README because it is full of both general insights and postgres-specific insights about how to migrate production relational databases (using expand and contract pattern).

github.com/ankane/stron...
GitHub - ankane/strong_migrations: Catch unsafe migrations in development
Catch unsafe migrations in development. Contribute to ankane/strong_migrations development by creating an account on GitHub.
github.com
November 20, 2025 at 4:10 PM
For one, it is important to get familiar with the PostgreSQL docs.

More so because you want to be comfortable going to the authoritative source when questions come up. The statement synopses are tricky to read, so practice helps.

Also the manual is good reading if you want to learn something new.
November 20, 2025 at 4:08 PM
This person already has an "apprenticeship project" which gives them a test bed to experiment, run queries against real(ish) data, and not be too scared to break things.
November 20, 2025 at 4:01 PM