OneQuery VS Metabase

Have you used Metabase or Apache Superset for job data visualization? How do they compare to building from zero?

Metabase

Metabase | https://metabase.com/ | REMOTE | Full-time | Frontend and Backend Engineers

Metabase is an open source (https://github.com/metabase/metabase) business intelligence software that lets anyone in your company rummage around in the databases you have. It connects to a number of databases / data warehouses (BigQuery, Redshift, Snowflake, Postgres, MySQL, etc).

Here's a dashboard about us: https://stats.metabase.com/public/dashboard/92d6b7ea-7526-48...

People rather like the product (https://metabase.com/love). We're a remote team full of people who care about user experience, making complicated things as simple as possible and building things. We have a deeply pragmatic engineering culture and value building things that people actually use vs whatever closes a deal or makes for a good press release.

Tech stack: Clojure on the backend, Typescript and React on the frontend

We've posted in several "Who is hiring" threads in the past with good success, we hired quite a few folks from these posts!

Frontend Engineer role:https://jobs.lever.co/metabase/8f02d3fa-edf4-4433-a6d1-4f9e5...

Backend Engineer role: https://jobs.lever.co/metabase/85f454d8-e795-4978-8a2b-4b8bf...

Metabase to build dashboards

Hope you enjoy the release. If you want to get into the nitty-gritty, check out our release notes in GitHub. To see what other features we have in the works, see our product roadmap.

I've found the Metabase test suite[0] to be very good considering it's real-world software written by a for-profit company. Coverage is good, the correct tests usually break when doing a refactor (stuff like "Oh, I thought this change was harmless but actually it breaks the permissions model"), etcetera. But the most important thing is that there's a strong team culture of a) demanding good tests on each PR b) hunting down flaky tests and other sources of friction.

Another neat thing was that there used to be a full-time SDET who spent a lot of time writing Cypress reproductions for known bugs. When you picked up the bug, you could un-skip the test that was right there waiting for you.

All that said, of course it's far from perfect!

0: https://github.com/metabase/metabase/ Backend unit tests are in test/, Frontend unit tests are in frontend/test, end-to-end tests (Cypress) are in e2e.

I've seen something that looks like AI-assisted root cause analysis on PRs: https://github.com/metabase/metabase/pull/57503#issuecomment...