Nico s thread this week (green tests, 5.5 hours down) reminded me of a smaller version of the same problem on the B2B AI product I manage.
The scene: a data preparation job finishes and the row turns green with Completed . The customer reads that as checked and safe to use . It means ran without errors . Weeks later someone asks why a model was trained on a version nobody signed off on, and the status page says everything was fine.
It's here. Vercel Day is live today on Product Hunt.
750+ products launched with the vercel-day tag everything from AI coding tools to desktop assistants to one app that simulates fMRI data on your pitch deck. The range is wild.
Setting up a new business is tough, but growing it is tougher! So, what s the hardest part of growing a startup? What difficulties can a entrepreneur face and how can he/she overcome it?
Three of today's launches ship a confident number at the user. How much of this page is AI. How far this repo sits from production ready. How many hours of debt that represents. Different products, same move.
The problem isn't accuracy. It's that nobody can tell you when it's wrong. A linter points at line 40 and you either agree or you don't. A 0-100 score for something unmeasurable can't be argued with, so it never gets corrected, and it trains people to either ignore it or trust it for no reason at all.
Every quarter, I set goals and then review how I did.
I started doing this two years ago after realising that New Year's resolutions simply don't work for me. To be fair, I don't always hit my quarterly goals either, but my success rate is much higher.
Unit tests are great for making sure buttons click and forms submit but they are completely blind to a modal moving 5 pixels to the left or a background color bleeding into a header.
We started running automated headless browser screenshots before and after restyling PRs to catch silent layout breaks.
I am currently working on an idea with my team. All of us have jobs and are in different locations(same time zones). We're are struggling with productivity because only two members are fully commited on building the product. The two of us came with up with the idea and we brought two members who shared interest and the vision of the idea. The two other guys will promise to do stuff and then not deliver on them. How do you motivate them to work without being intrusive to their time. And how do you make sure they not slack?
