Blazer VS forem

I try to avoid these tools wherever possible, given the choice I'd always go for tools like Blazer.

https://github.com/ankane/blazer

No such luck in my current role, Looker and PowerBI are both in use by different bits of the org and nobody has the ability to delve into the underlying figures.

As u/jaxn said you could use Blazer for this kind of thing. I would also look into materialized views or custom tables and a scheduled job that calculates the metrics they care about. That will take you a long way. Eventually you can use something like Metabase but I would put that off for as long as possible as it's really expensive and pretty involved.

And it's Open Source: https://github.com/evidence-dev/evidence

I'd also highly recommend Blazer https://github.com/ankane/blazer if you are into the Ruby on Rails world. It's super solid, and it's been an indispensable tool integrated to all my projects.

I use Ahoy too, but I don't have very good visibility into the data. I should spend more time building queries and creating charts. I should probably set up blazer as well: https://github.com/ankane/blazer

blazer

The Blazer gem provides a nice way to analyze the results easily. It is simple to install and allows SQL queries to run against tables. The query here shows that the candidate implementation is significantly faster than the original.

I even opened a discussion, which got no responses so far (which I think existed somewhere else or I am the only one with this issue...).

Whether you're sharpening your JS skills, making PRs to your OSS repo of choice 😉, sprucing up your portfolio, or writing a new post here on DEV, we'd like to hear about it.

Add articles clickbait_score as factor in final feed ordering #20493

Do more documentation-related and code contributions to Forem's repository

This year again, I contributed to DEV with multiples ways, I've contributed very little to the repository, moderated the bad posts quite a bit, and welcomed newcomers to the platform. I feel that a place like this should always be so welcoming to users, so why shouldn't I?

docs: making updates to Editor Guide #20258

Forem - Open Source Alternative to Circle

Whether you're sharpening your JS skills, making PRs to your OSS repo of choice 😉, sprucing up your portfolio, or writing a new post here on DEV, we'd like to hear about it.

We like to (loudly!) remind everyone here that the DEV Community is powered by Forem, our community-driven open-source platform. Central to Forem's continuous improvement are the efforts of our dedicated volunteers and we like to highlight those who have gone above and beyond to help out and submit PRs to our repo.

Note: There's a PR on the Forem repo open for this. Check out if it has been implemented before trying this!