I have written a lot of server side code in dynamically typed languages (mostly Python) with a variety of database systems (I started my career in the mid 2000s

I have written a lot of server side code in dynamically typed languages (mostly Python) with a variety of database systems (I started my career in the mid 2000s on ZODB, an object-oriented database). At least in my experience the "philosophical" language-database pairing always ended up being much less important than the database own strength and weaknesses in regards to the problem being solved. For me Postgres is the best default choice if you don't understand that well where your project/product is going (Not saying it isn't a good choice later on as well). Out of the box it handles pretty much every use case I encountered at least good enough for a long time without adding supplemental data stores or ugly hacks. For me the difference in development barely matters. Locally schema changes are pretty much friction-less with the right tooling, and in production the problem is usually not changing the schema, but the existing data. The latter being a pain in any tech I have used so far, because often it is not even an engineering challenge but a matter of business decisions.