<oembed><type>rich</type><version>1.0</version><title>VitorPamplona wrote</title><author_name>VitorPamplona (npub1gc…fnj5z)</author_name><author_url>https://yabu.me/npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>Diminishing returns is one of the most misunderstood concepts in engineering. &#xA;&#xA;Most devs know they can do 80% of the work very fast, but that last 20% will consume their soul and 10 years of their life. Because of that, their minds think it&#39;s not worth investing in the project anymore: &#34;I could be more productive in this new side project&#34;. Which is true, but that also means that you have two half-baked projects that nobody can use because they are not finished. You fail on both at the same time. &#xA;&#xA;In the market, diminishing returns are diminishing returns for everybody. To have the best product, you focus on diminishing returns exactly because your competitor will phase out and give up: &#34;it is too much money for little gain&#34;. Any rational player will decide against it. But, if you truly want to win, you must keep pushing your product&#39;s edge up. You must work through diminishing returns profitably. If you don&#39;t, you are already gone, and your competitors are going to love it.&#xA;&#xA;Learning the law of diminishing returns is not done so that you can avoid it when it happens. It&#39;s done so that you can go through it in a way that makes sense.</html></oembed>