As far as keeping track of domain changes you can store DDL files in version control like you mention or use tools like Flyway (https://flywaydb.org) or Liquidbase (https://liquibase.org) which takes care of database migrations. Source: about 2 years ago

I just use SQL directly (or something like JOOQ). For database migrations I use Liquibase. Source: about 2 years ago

Regarding the migrations, there are tools such as https://liquibase.org/ or FlyAway that handle this. Heck, you can even use an ORM that has a migration baked-in but that defeats the purpose of having the migrations in a separate project. Source: about 2 years ago

I've trialled schemachange and liquibase which are change script based tools. I've ruled out a whole load of other tools that are either change script based tools or don't support Snowflake, including the following:. Source: over 2 years ago

Nowadays I prefer to automate database updates and deployment, using Liquibase and its relational database vendor agnostic syntax for that. Especially on production systems. But on local dev environments, I can still use the occasional SQL in a pinch. Source: over 2 years ago

I think deepart.io was the first free style-transfer tool. Source: almost 2 years ago

Https://deepart.io is a bit weird sometimes. But if you fiddle with the settings for a bit it's really good. Source: almost 2 years ago

I wouldn't. It's clearly one of the deep learning filters slapped over a screenshot. It's low effort and anyone can make it using something like this https://deepart.io/ something done by hand would look so much better. Source: about 2 years ago

Use an ai site like deepart.io, input the picture, and then an image of a drawing you want to recreate the style of. It basically recreates the image but in the style of the drawing. Source: over 2 years ago

For those of you looking to try this out too, visit https://deepart.io/ Or Google for style transfer AI. Source: over 2 years ago