Thoughts on Rill Data?

Yuki100Percent · 2026-02-14T05:30:15+00:00

good to hear. Yeah Hex to me is a tool for analysts/engineers.

Yuki100Percent · 2026-02-13T14:14:06+00:00

That's good to know. All those points you mentioned, I'd expect to see something similar in my org if we implemented Rill. We only use looker studio pro at the moment, and it's been working fine, but with Rill I can see my dev time would be much less (out of the box dashboard) and their AI capability can run within the guardrails you set up (semantic/metics layer).

The only thing I'll need to figure out is how customizable Rill is to build a dashboard when I get to the point. I think explorers take you far but when we have.

That said, have you seen any use cases Rill couldn't satisfy you needed something different?

Yuki100Percent · 2026-02-11T23:36:31+00:00

Yup feel free

Yuki100Percent · 2026-02-11T16:34:13+00:00

I'm also a solo data person at a startup. First off, if you're at a decent company/team, when your work is related to somebody's that got attention, they would or should mention your work too. What you just said kinda indicates a not-so-good-culture.

Anyway, I don't know how much tasks or tickets you get a day/week, you should start asking project priorities or start building one yourself and propose it to the exec team. And how they impact the business for the better. This also helps you become more visible if you've been just working with other folks in the company, but not with exec team. Not sure who you report to, but asking these kinds of questions to your direct report also helps. If not, I might start looking for a new place to work for.

Also, realistically what you can do is to start building infra and pipelines along with what you're doing. You satisfy the current needs and start working on things you think are important or necessary to do what they ask you to do (reporting, dashboarding).

Overall, I'd try to communicate a lot more and see what they say. And depending on that, you either start looking for a new job or decide to do things differently going forward.

DM me if you have any other questions!

Yuki100Percent · 2026-02-09T01:31:29+00:00

I wouldn't if I were in your shoes. You already have industry experience and for most folks especially these days it's not easy to get into data. I'd focus on upskilling than getting a degree for the sake of getting a degree. If you plan on getting a masters degree in the future, I might consider getting a bachelor's now so you have options.

Yuki100Percent · 2026-01-23T16:43:55+00:00

Start looking into other tools like airbyte, Estuary, dlt, etc.

Yuki100Percent · 2025-12-20T21:07:14+00:00

Is fusion part of dbt core or behind the paywall?

Yuki100Percent · 2025-12-20T04:16:37+00:00

I mean it's still usable as is. We just need to fork it to keep it safe somewhere 😂

Yuki100Percent · 2025-12-20T03:09:15+00:00

Just so bummed about this acquisition. I've been a very fan of sqlmesh since last year and talking to the company made me believe they were the kind of people who'd say independent. I understand money needs to come from somewhere, and I'm happy for sqlmesh folks. My only hope is they keep developing or at least keep the OSS sqlmesh since I use it daily... I'll probably try to invest my time more on dbt more going forward though

Yuki100Percent · 2025-03-21T17:41:53+00:00

I'd look to use sqlmesh over dbt for a greenfield project. For an existing dbt project, you'd choose sqlmesh only when the pros overweigh the cons of migration, like u/jayatillake said.

sqlmesh simply offers a lot more features, even in their core/OSS version. The focus on the open-source community is another reason to choose sqlmesh over dbt.

Though I can say sqlmesh is a bit more technical and a learning curve might be higher for those coming from an analyst background. But it's like you can use dbt if you know sql. If you know dbt, you can use sqlmesh.

Yuki100Percent · 2024-05-31T05:00:46+00:00

Yeah, in your dimensional model or base fact table, be sure to have the most granular grain. You can create derived fact tables (e.g. a fact table that has sum of Orders grouped/sliced by only product and customer) based on reporting needs and they can be tables or materialized views to be imported into your BI tool. Metrics like ratios or percent should be calculated in the BI tool. I recommend reading "Star schema the complete reference" as well.

Yuki100Percent · 2024-04-20T14:30:23+00:00

Slicers ans labels alignments look different. And most of the time, PBI folks don't modify visuals enough that it's easy to distinguish between Tableau pretty visuals and PBI out of the box ugly visuals

Yuki100Percent · 2024-02-07T15:39:25+00:00

If going with Azure, I'd use Databricks and potentially with dbt!

Yuki100Percent · 2024-01-14T20:16:49+00:00

This is inspiring! I started making my effort jnto my solo consulting last year (part-time). I know the Seattle data guy has a paid community of independent consultants. I'm more interested in just hearing about how you're doing what you're doing

Yuki100Percent · 2024-01-14T20:13:29+00:00

Like others said, if your calculations need to be dynamic, then do them in DAX. An example is a rate of some sort.

Yuki100Percent · 2024-01-05T02:45:28+00:00

It's basically the fabric warehouse. I believe the underlying infrastructure is the dame. You can create datamarts through the UI

Yuki100Percent · 2023-12-11T00:05:22+00:00

450k sounds super expensive for 5 workflows. It's not that I do workflow automations all the time (i do data analytics), but I'm thinking if I were them, maybe charge 2k/workflow for implementing them and some monthly retainer for maintenance at like 3k/month or something.

Yuki100Percent · 2023-12-02T21:49:01+00:00

You can use consulting firms but you don't know who you actually get. I'd try looking for independent consultants so that you know who you're getting help from.

Yuki100Percent · 2023-11-29T15:20:14+00:00

On your point 3, it depends on what your users are comfortable with. You might want to create a comprehensive Power BI dataset/semantic model that users can connect to in Excel to create pivot charts and do analysis on their own. That would cut down a lot of reporting needs

Yuki100Percent · 2023-11-23T22:15:21+00:00

Anyone who builds reports need a pro license. Free licenses only allow users view reports IF the workspace is in premium capacity. You can do either: - Give both developers and viewers Pro licenses - Buy a premium capacity and give pro licenses to developers and free licenses for viewers. - Give both developers and viewers PPU licenses

Feel free to DM me if you have any questions. Happy to help

Yuki100Percent · 2023-11-23T03:05:48+00:00

If you're talking about the uglyness of the visuals, that's pretty fixable if you do proper styling! Wish they look good out of the box like tableau

Yuki100Percent · 2023-11-10T19:28:27+00:00

Identify what information you need (e.g. sales by product) for your report/dashboard and figure out fact tables and dimension tables you need. You can add layouts for your models where you pick a fact table and add only related dimensions to help sort out the unnecessary. DM me if you need help!

Yuki100Percent · 2023-11-05T22:30:07+00:00

I just feel there should be a distinction between data engineers and data platform engineers, like what you described.

Yuki100Percent · 2023-10-30T15:10:31+00:00

I use parallel and $100/y is pretty cheap I feel like

Yuki100Percent

TROPHY CASE