Why I'm Building a Local-First Developer Cockpit

When I changed of company, I joined a team of four members that use emails and a dedicated Slack channel to share local dev errors to the whole team so that more experienced devs can have a look (in parralel with they work) and give hints to fix that error. The idea sounds reasonable: share errors with everyone, someone could help to fix them. Here's what actually happens. The error emails were piling up, mixing with preprod and prod exception fired seventeen times because many users (or one user hitting many times that buggy button) hit the same page before anyone noticed. Production noise mixes with preprod noise. And on top of it all: MR notifications, CI alerts, calendar invites, Slack threads about train issues. So I did a rational thing — I stop reading. The channel that was supposed to surface problems becomes part of the background noise. I've seen this pattern on teams of 5, when I was seating in the same room, now the team grown to 10 members, I moved and I'm full-remote, and