Vibe Driven Development
robinrendle.com
robinrendle.com
It’s also a function of what phase the product is at. Do you have users yet? Do they use the product yet? Do they stay retained? What features matter to them? All of those questions are very quickly answered with data. They help align a group of collaborators on what matters.
I disagree.
It's more of "Make a good enough product" with emphasis on trying ot yourself to see it's actually good enough. Finish up, try it out, then ask yourself "does this feel good to use?: or did you puncture your finger on some splinters?
The author has a successful business which he achieved following this mindset, so there is definitely merit in what he's talking about.
The author's main point is that too much of that data is shit, and thus following them will lead to shit.
This part is a highlight for me
> They’ll say “this user is 4.5% happy” and, okay, great. Now what? This numerical value sure is bullshit but it’s not even helpful bullshit because these numbers never explain why things suck.
> (Just look at the product and it will tell you why it sucks.)
And
> It comes down to this annoying, upsetting, stupid fact: the only way to build a great product is to use it every day, to stare at it, to hold it in your hands to feel its lumps. The data and customers will lie to you but the product never will.