u/EmmaJohnson19

I once added a small “temporary” condition to skip an error during a release because we didn’t have time to fix the root cause. It was meant to be removed after the sprint, but it stayed there for months, and other code slowly started depending on it. By the time someone questioned it, nobody remembered why it existed, but everyone was afraid to delete it because “it might break something.”

Mine was a "small" hotfix before a release that ended up taking down half the system. We fixed it quickly, but the postmortem was longer than the actual outage. What's your story?

I am creating a dashboard, in that I want to add only one more widget but it has too much data to contain in one chart, so What chart type should I use for this? any recommendations?

I am looking to change my reporting platform.

I once added a small “temporary” condition to skip an error during a release because we didn’t have time to fix the root cause. It was meant to be removed after the sprint, but it stayed there for months, and other code slowly started depending on it. By the time someone questioned it, nobody remembered why it existed, but everyone was afraid to delete it because “it might break something.”

I’ve run into this where incremental refresh worked fine for the fact table, but changes in the dimension table quietly shifted historical numbers. At first, it looked like a DAX issue, but the real problem was that the model wasn’t preserving the old dimension state. Curious how experienced Power BI devs usually handle this fix it in the warehouse with proper SCD logic, or manage it inside Power BI somehow?

I once built a sales dashboard where the SQL was fine, the visuals were fine, and everyone approved it in testing. Then after launch, every team wanted their own version of the same metric with slightly different logic. Revenue

I once added a small “temporary” condition to skip an error during a release because we didn’t have time to fix the root cause. It was meant to be removed after the sprint, but it stayed there for months, and other code slowly started depending on it. By the time someone questioned it, nobody remembered why it existed, but everyone was afraid to delete it because “it might break something.”

I once built a sales dashboard where the SQL was fine, the visuals were fine, and everyone approved it in testing. Then after launch, every team wanted their own version of the same metric with slightly different logic. Revenue meant one thing to finance, another to sales, and another to management.
The most annoying part wasn’t building the dashboard; it was getting everyone to agree on what the numbers actually meant.

I am creating a dashboard, in that I want to add only one more widget but it has too much data to contain in one chart, so What chart type should I use for this? any recommendations?