mjaniczek

Thanks for the "Ski-bi dibby dib yo da dub dub" earworm

I wonder what the modus operandi of preset makers is. Like, the "Boards of Casio" patch data here is amazing, usable, playable. But the official patch banks of many synths, VSTs etc. are quite unusable. Maybe they're aiming to show the breadth of what sounds you can get out of it, rather than provide good defaults?

I like the idea of a fast Spotify player, but I can't get over my doubts of LLM code quality when the audio playback stutters even with the 200ms output buffer setting (on macOS).

AI blindness is making my reviews of others' PRs harder and harder.

Congratulations to Hillel for finishing the book!

Thank you for another check on my bingo card.

The choice to use Count was made before I joined the company; IIRC they migrated to it from Tableau.

We wanted to migrate (to Streamlit, back then) to have the SQL not live locked in a tool, but inside our git repository; to be able to run tests on the logic etc. But the spaghetti mess was felt too, even if it wasn't the main reason to switch.

(But then, 1) some team changes happened that pushed us towards Metabase, and 2) we found that Streamlit managed by Snowflake is quite costly, compute-time wise. (The compute server that starts when you open a Streamlit report, stays live for tens of minutes, which was unexpected to us.)

----

Export to DBT sounds great. Count has "export to SQL" which walks the graph of the cell dependencies and collects them into a CTE. I can imagine there being a way to export into a ZIP of SQL+YML files, with one SQL file per cell.

Look at count.co for a Figma-like approach to databases.

We were using it at work (transitioning to Metabase); it's great for exploring and debugging and prototyping but it ends up too much of a tangled spaghetti mess for anything long-term. Would not recommend for user-/other-company-departments-facing reports or dashboards.