3 ms·

A rather painful reading experience. The author needs to learn how to edit their thoughts and use punctuation/grammar properly.

• defnmacro 6y ago
  A brief exercise in shipping an MVP and seeing if it gets traction before refining the feature set =). Thanks for reading my ramblings despite the lack of proofreading hopefully its a bit better for others now.
  • internetslave 6y ago
    Haha I appreciate this response.
  • antaviana 6y ago
    What came to my mind when reading the unedited copy is that you are confusing MVP with prototype. An effective MVP is something that does relatively very few things but that does them well or very well. Otherwise your churning will be huge. In other words, I read your post completely but it was somewhat painful because the copy was not polished for clarity, so I doubt I read a second one. I churned. To build effective MVPs you need to keep an eye on quality. Do fewer things that work flawlessly will have much more impact than throwing a bunch of things to the wall. You need to make a culture change and overweight quality. And I also recommend B2B if you happen to be trying B2C.
  • lmarcos 6y ago
    "I didn't have time to write a short letter, so I wrote a long one instead". As a "tech guy", I never understood the notion of MVPs. Sure, start small makes sense, but delivering something half baked just demonstrates one doesn't care enough for their readers/customers. Why would anyone like to put himself in such a position?
    • yjftsjthsd-h 6y ago
      Because people emphasize "minimum", when the important part was "viable product".