mattytwoshoes
mattytwo.shoes
mattytwoshoes
@mattytwo.shoes
Decision Engineer, Data Educator & Consultant
For me this is not just "opinionated" but simply optimising for a single criteria. I suppose other approaches with a single-criteria focus could be "security" or "privacy", where all other factors are essentially ignored...
October 27, 2025 at 8:45 PM
...data team members might ingest and load data by dumping CSV files to their machines from sources and then manually import them to the database
October 27, 2025 at 8:44 PM
...they might run Metabase in a Docker container and run it off a laptop that sits in the office, that employees VPN into to access dashboards...
October 27, 2025 at 8:44 PM
If the primary restriction is budget, then all tool choices will be made with this criteria in mind. For example, all analysts might run local IDEs and connect to a production Postgres database that they share with developers...
October 27, 2025 at 8:44 PM
Don't forget about budget data stack, where the only thing that matters is CapEx per month/year
October 27, 2025 at 2:36 PM
i cannot stop laughing at this
September 23, 2025 at 11:30 PM
I use time.is a lot for their spreadsheet-like view (time.is/compare) and it's awesome
August 19, 2025 at 8:49 PM
its about how to pronounce Bulbasaur isn't it
July 15, 2025 at 9:42 PM
Nurdle - Wikipedia
en.wikipedia.org
July 15, 2025 at 9:39 PM
The blob of toothpaste on your toothbrush is called a nurdle.
July 14, 2025 at 9:37 PM
that would be an insanely awesome session if you combine it (somehow) with some data stuff ;)
May 25, 2025 at 7:49 PM
oh boo :( did you try some of the aliases too in the dropdown?
April 29, 2025 at 9:08 PM
sharklasers
you're welcome :D
April 28, 2025 at 3:40 PM
I'm at 0.13 😒
March 23, 2025 at 11:53 AM
When using it downstream, you can do COUNT(unique_eventid) and not have to worry about duplicates, but if you want to split by dimension you'll need to build a way to select a key from the JSON and do JSON_EXTRACT() - we did that process using count.co fairly easily in a canvas.
March 12, 2025 at 9:42 AM
For example, I designed a compromise by creating a user actions table that has a JSON column for additional dimensions. As dimensions change per action (i.e. onboarding stuff shows which channel someone came from, but conversion actions have revenue values) this was a good way to overcome this.
March 12, 2025 at 9:42 AM
I do believe it's possible to store a lot of logic in the pre-processing stages before data is used in reporting, data products etc. but as others have mentioned, it's always a question of tradeoff.
March 12, 2025 at 9:42 AM
To answer the original question, I think the term is a little silly. We can just name things more explicitly, i.e. "moving logic upstream to the warehouse" rather than rely on the notion that everyone will know what this marketing slogan means.
March 12, 2025 at 9:38 AM
This term only makes sense if you draw your diagrams from left to right, which is a common assumption that we do this in the West but I am not sure about countries that write right to left...
March 12, 2025 at 9:36 AM
If I told you I had it and that you should trust me, would you believe me?
February 27, 2025 at 10:22 AM
it tastes good on its own 🤣
February 12, 2025 at 2:12 PM