sqlfluff VS Metabase

This linter can really enforce some best practices https://github.com/sqlfluff/sqlfluff

A list of best practices:

BigQuery SQL and SQLFluff

There's a SQL parser/linter called SQLFluff that my team uses for our CI/CD. I've made a few pull requests to fix the parser for the particular SQL dialect we used, and my college compiler classes definitely helped.

Include bells and whistles to impress the reader: Most projects will have the common things like ETL scripts (e.g. SQL, Python, Airflow, dbt, etc) covered. To go the extra mile and stand out, you should also include things like data quality tests (e.g. dbt tests, great expectations, soda), linting scripts (e.g. sqlfluff, black), CI pipelines that check for linting and unit tests for ETL code before code can be merged to main (e.g. github actions). Include instructions on how to run those tests or linting or CI pipelines in your README file and include screenshots of the success or failure output to give the reader an example.

Capitals I pretty much auto write, although I'll used the code formatter I wrote if someone sends me something messy. Bad and reused aliases, however, require manual fixing before I can get to the code review stage, so a PR using those will be rejected as needs work. sqlfluff is a decent formatter & linter if you need to get into details like that regularly.

SQLFluff

Not serving all of our needs but it did its job: https://github.com/sqlfluff/sqlfluff

sqlfluff – A SQL linter and auto-formatter for Humans

Metabase | https://metabase.com | REMOTE | Full-time | Backend, Frontend, Full Stack, and DevOps engineers

The two best:

1) Working (professionally) on a project that happens to be open source: https://github.com/metabase/metabase/

2) Coming to a Rails project mostly written by a very senior 7-person team. There was still a fair amount of jank (mostly from seed-round assumptions that weren't holding up when I joined after the Series A) but it still followed The Rails Way and nothing was too gross. It also helped that everyone important was still at the company and available for questions.

PS on (2): Seven of those original eight dev are now gone, including me; the median years of experience has gone from 8-10 to 0-3; the team size is at least 40 and I think more; and my understanding from friends still at the company is that the codebase is in general a flaming mess.

Try metabase.com its built with node and uses plugins.

Where do they use Node? The main code is written in Clojure.

Metabase | https://metabase.com | REMOTE | Full-time | All Roles We’re hiring for multiple positions across the team. Metabase is open source analytics software that makes it easy to ask questions of your data. It works with most databases / data warehouses (BigQuery, Redshift, Snowflake, Postgres, MySQL, etc) and has a simple and powerful UI and UX that lets anyone in your company ask their own questions. Tech stack: Clojure, Javascript, React, Redux, AWS, Postgres, K8S (EKS)

Metabase | https://metabase.com | REMOTE | Full-time | Backend, Frontend, Full Stack, and DevOps engineers

We're hiring for multiple positions across the Engineering team (and in many other non-engineering roles).

Metabase is open source analytics software that makes it easy to ask questions of your data. It interfaces with a number of databases / data warehouses (BigQuery, Redshift, Snowflake, Postgres, MySQL, etc) and has a simple and powerful UI and UX that sits on top of it.

Tech stack: Clojure, Javascript, React, Redux, AWS (ECS, Autoscaling, Aurora, RDS, SecretsManager, S3)

Roles: Data Analyst, DevOps, Frontend and Backend Engineers, Growth, and many more roles.

See https://www.metabase.com/jobs/

Metabase