<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software on Random Ramblings</title><link>https://blog.foundev.pro/tags/Software.html</link><description>Recent content in Software on Random Ramblings</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 20 Dec 2018 20:00:00 +0000</lastBuildDate><atom:link href="https://blog.foundev.pro/tags/Software/index.xml" rel="self" type="application/rss+xml"/><item><title>MVP how minimal</title><link>https://blog.foundev.pro/2018/12/20/mvp-how-minimal.html</link><pubDate>Thu, 20 Dec 2018 20:00:00 +0000</pubDate><guid>https://blog.foundev.pro/2018/12/20/mvp-how-minimal.html</guid><description>&lt;h1&gt;MVP how minimal&lt;/h1&gt;&#10;MVPs or Minimum Viable Products are pretty contentious ideas for something seemingly simple. Depending on background and where pepole are coming from experience wise those terms carry radically different ideas.&#10;In recent history I've seen up close two extreme constrasting examples of MVP:&#10;&lt;ul&gt;&#10;&lt;li&gt;Mega Minimal: website and db, mostly manual on the backend&lt;/li&gt;&#10;&lt;li&gt;Mega Mega: provisioning system, dynamic tuning of systems via ML, automated operations, monitoring a few others I&amp;rsquo;m leaving out.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="feedback"&gt;Feedback&lt;/h2&gt;&#10;&lt;p&gt;If we&amp;rsquo;re evaluating which approach gives us more feedback, Mega Minimal MVP is gonna win hands down here. Some will&#10;counter they don&amp;rsquo;t want to give people a bad impression with a limited product and that&amp;rsquo;s fair, but it&amp;rsquo;s better than no impression (the dreaded never shipped MVP). The Mega Mega&#10;MVP I referenced took months to demo. only had one of those checkboxes setup and wasn&amp;rsquo;t ever demod again. So we can categorical say that failed&#10;at getting any feedback.&lt;/p&gt;</description></item></channel></rss>