This is not really a problem introduced by the thing in the article, but the "UI" for duckdb just kinda sucks. When I want to interactively explore some data, I want to easily add conditions and aggregates, but there's nothing in the Duck UI that actually does this. It will make a little table of the top 20 values of irritating_column_name but there's not a 1-click way to add `where irritating_column_name = 'incredibly inconvenient value'` to the query and re-run, which is an absolutely basic data exploration feature.
Based on this comment, you might enjoy the Malloy data language. It compiles to SQL and also have an open source explorer to make filters like what you are saying easy.
Thanks for the tip. I am checking it out right now.