Show HN: Meridian(PH#1) A better way to recognize developer contributionsHi HN! We built Meridian because we kept seeing the same thing: developers get estimates for planned work, and then spend a huge chunk of their time doing everything that wasn't planned.Debugging something weird, helping a teammate, reviewing PRs, jumping on an incident, fixing a flaky test, answering questions, etc. All useful work, but a lot of it never makes it back into the estimate.So when the sprint slips, it can look like the estimate was wrong, when really, a bunch of other work happened in between.Meridian is our attempt to make that work visible and better account for it. We’re building it in the open and open sourcing it because we’d much rather have developers tell us where we're getting this wrong than build another productivity dashboard in a vacuum.We launched last week and ended up #1 on Product Hunt, which was pretty wild. Now we're looking for feedback from the core dev community.Curious how you deal with unplanned work today, and whether this is actually a problem wo