Hacker News Reader

Comment by productceo | Hacker News Reader

Let me know when you would like me to invent yet another word to call the same thing. How's Minimum Promising Product?

If MVP does not solve a real problem, it does not validate the correct hypothesis, so what the post describes as an MVP that is not MLP is not an MVP.

And an MLP executed to be not MVP would be a thing built to be built, or taking unnecessarily risky bets spending unnecessary cost.

Cut the crap with fighting words with words. If the community used the word MVP to help introduce a more useful concept, real builders focus on executing it correctly, to the best of our ability, giving the inventors fair credit and most charitable interpretation. Alas, we have content marketers among us, and those who failed and wish to blame it on being given wrong instructions to follow, inventing empty words like MLP.

View on HN

Why are you so upset about words? if you don’t like a word, don’t use it or make up your own! it’s a beautiful thing.

A word you create because you don’t like another word is called a blortle. I just made it up.

no cap?

cap

I like it! Seems to happen quite a bit in academia (e.g. microbiology)

I don’t like blortle, I would prefer a raifin. See? I’m already blorting

What’s the etymology for yours? Mine is blurt + -le (the diminutive, not the frequentative)

Does our word need an etymology? Looks to be beyond MVW scope. (or should I say MLW here?)

A word you create because you need a random word is called a fizz, and when you need another fizz you call it a buzz.

the trigger is recently joining an organization or getting a new CEO or manager that uses these cringy aspirational unnecessary words

and listening to the entire internet say "if you don't like one tiny aspect of your work environment, its a huge red flag for a bunch of other stuff so just leave!" as if such choice in the matter is really there and that the next organization doesn't have some other tiny cringy thing

so then if you ignore that advice, you're stuck with the childish babble that the people in your organization use to cope

I just ignore stuff I don’t like, it’s a lot easier.

Interesting to see the other POV. I experienced this from the opposite side.

A teammate once told me he is frustrated with being asked to work on an MVP, that is minimum cost, minimum polish, minimally functioning. He said he wanted to work on MLP, so I said he can call it MLP if he wants, but what we must build does not change: prove the concept minimally such that we can verify whether the problem we seek to solve is a real problem in the first place, then we can add as much polish as needed once we know it's a good problem to solve. If we think customers are experiencing some problem that, in order to solve minimally, we need to give them polish, then the polish is a part of the MVP/MLP. Otherwise, it is not. It doesn't matter what we call it. What matters is what we must do.

He thought that my attitude taking the distinction between MLP and MVP lightly was a sign that I do not care about the best interest of our customers, and left the company.

Reply on news.ycombinator.com