The Diminishing Returns of Everything

I can see why it <i>feels</i> this way, but often times it seems to me the opposite is true, like a phase transition: it remains a bunch of commits until at some point it &#x27;suddenly&#x27; becomes a product, usable by the designated users, solving a problem, possibly generating revenue. Like water that cools and cools and eventually turns to ice, even though that last quarter degree didn&#x27;t change the temperature a lot.

<i>&gt; The only exception to this rule I can think of is McDonald&#x27;s fries. The more you eat, the better they become. It is true.</i><p>Potato chips are, to me, an even more perfect example of this effect. They are engineering marvels. If a food is too salty, you eventually crave something sweet. Too sweet and you get tired and want salt. Potato chips take the sweetness of potato starch and add <i>just</i> the right amount of salt to keep you balanced.<p>The satisfying crunchiness gives way to carby creaminess, which then promptly dissolves entirely, leaving you feeling like you haven&#x27;t consumed anything at all [1], so surely one more chip is OK, right?<p>Potato chips are my crack. If I could eat them unburdened by shame or the desire to take care of my health, I would eat them until I burst.<p>[1]: <a href="https:&#x2F;&#x2F;www.nytimes.com&#x2F;2013&#x2F;02&#x2F;24&#x2F;magazine&#x2F;the-extraordinary-science-of-junk-food.html" rel="nofollow">https:&#x2F;&#x2F;www.nytimes.com&#x2F;2013&#x2F;02&#x2F;24&#x2F;magazine&#x2F;the-extraordinar...</a>

&gt; For instance, I spend the past two days working on a single CSS file, in an attempt to center-align some stupid buttons (a futile attempt, since they are still not aligned). In comparison, at the beginning of the project, I built out the entire REST backend of the web app in a single afternoon.<p>It could be argued that the value of the REST backend is lower than the value of the stupid buttons: since the backend is so simple, everybody can do it, while the stupid button takes a wizard to get right. On the market, your commoditized REST backend will have to compete with other solutions on the quality of your stupid buttons.<p>Hence, spend even less time on the backend, by using auto-generators, and focus all your time on the button. Buttons are a big dollar business.<p>Damn, I wish a had a CRUD-auto-generator-business, this would be the perfect plug. Check out auto-crud-button-focus.com right now!<p>&#x2F;edit: adding the [irony] tag before I get more insulted &quot;WHAT???!?!?!?&quot;s (I know nothing about backend stuff, I work in embedded and electronics)

This is disingenuous. Sure, the first X hours of working on a new project are a lot of fun and you can set up the framework for what you&#x27;re doing and feel like you&#x27;re making great progress.<p>But what you&#x27;re missing is detail and quality. For example, I can set up the structure of my thesis by working out chapter titles, headings, subheadings and drafting bullet points per section. Straightforward. But doing the research and writing up takes years, it&#x27;s often boring, laborious and the net addition to the document can be as low as a couple of hundred words a week. It doesn&#x27;t mean the actual work is less valuable as time progresses.<p>Likewise let&#x27;s consider a software development project. We can make grand strides in the first X weeks, gathering requirements, creating user stories, creating tasks, sprints, assigning work, setting deliverables, setting up the various ceremonies. But at some point it boils down to writing some code, often boring, time-consuming, detailed and slow. It doesn&#x27;t mean the contributions made later in the project are any less valuable than the frantic hive of activity in the beginning.

I don&#x27;t really like the emphasis on &quot;wasting&quot; time, the way he wrote it in the bathroom light automation section. If you do not enjoy tinkering with voice activation (or X thing in the general sense), then I can see why you wouldn&#x27;t like losing time, but I would probably feel like it was 5 hours spent learning about home automation and voice control, which could maybe be applicable in other cases, both within home automation and outside of it. I don&#x27;t see the 3 hours mentioned as &quot;lost&quot;, but as time spent learning.

That&#x27;s why you pay contractors &#x2F; specialized people.<p>A 2-day electrical job would probably have taken me a month to complete working evenings &#x2F; week-ends, assuming no other house maintenance on the side, and the job would certainly have been sub-optimal and I&#x27;d have selected overkill components. Same goes about a plumbing job, it&#x27;s not rocket science, but working in tight spaces can be tricky&#x2F;messy, professionals know how to do it.<p>As for the backend, it&#x27;s easy to spin up if you know the tech, have done it a couple of times and know what to do. Given enough time, I could probably design an IoT gadget from the ground up. FPGA conception, ASIC design, then PCB integration, spin up, mechanical design, network interfacing, back &amp; front end services. But not only the end product will certainly be over-engineered, but it will have taken me 2 years to build and I would have no idea how to sell it.<p>I had a family member who cashed out in the SV and then tanked his next start-up. Long story short, he&#x27;s a business guy, not a tech guy. He lost 3 years on fairly simple MVP, then finally decided to pay someone, but it was too late.<p>I guess the morale of the story is to know ones own limits...

&gt; The first couple hundred lines of code of your project will have a much larger impact than the last few thousand lines of code ever will.<p>I think it&#x27;s easy to underestimate the importance of polish and fit and finish. In my experience a product&#x27;s success or failure is made in the last 20% of development, when all the fine tuning and bug fixing goes in to overdrive, and user experience is honed.

&gt; The first couple hundred lines of code of your project will have a much larger impact than the last few thousand lines of code ever will.<p>With this explanation, the author explains the diminishing returns by the fact that their value decreases (&quot;impact&quot;). I disagree: returns diminish because their cost increases. Assuming a thing can generate 100% of some value, the range 0-20% generates as much value as the range 80%-100%, but the latter range is more costly than the first range.<p>The return of centering the buttons is significant, because if they&#x27;re not centered then the product will look unprofessionnal, which is not good for business. It just happens than the cost of centering them is high, in this case as high as setting up the REST service in a first place.<p>The return of having your company survive is extremetely high. It just happens that this cannot be done with the first few dozens employees but with hundreds more, which is of course way more expensive.

&gt; The same goes for abs. The first ten thousand set-ups you do just may give you that 6-pack abs you want, but another thirty thousand sure won&#x27;t get you the 7-pack.<p>He picked the one type of exercise which doesn&#x27;t really change. If you&#x27;re lifting or running, you see <i>increasing</i> returns for a long time. You get stronger by lifting heavy weights, and you need to lift light weights to be able to lift heavy weights.

But let me put it in perspective, if I wasn&#x27;t wasting my time moving that button, I&#x27;d probably be watching youtube.<p>Is that wasted? Was it truly 3 hours lost for the OP trying to automate the light switch?<p>Nihilism. Do what you believe is worth it. Otherwise, don&#x27;t because it&#x27;s simply not worth it.

I think there is additional value to automating or improving a process even if the time spent automating exceeds the time saved by the automation.<p>What if it just makes me happy that I can turn the bathroom light on with my voice even though the time spent figuring it out exceeds any time saved by the automation?<p>What if I make a sucky task at work more approachable and easier by improving it? Rather than procrastinating doing the thing because I hate it, I pick it up and do it right away because I invested some time in making it suck less.<p>What if I gain skills automating one thing that make me more efficient on the next thing even if I&#x27;ll never recover the time spent on the first thing?

Re: the voice activated light class of idea. I have a weird NIH&#x2F;hoarding bug. I always try to do thing on my own (am now making electrical circuits). Somehow it&#x27;s a huge waste of time. Yet I know a ton of stuff and can fix some things, or avoid fear and scams.<p>One alternative is a hub of DIYers. Remember the story of how Xerox PARC operated ? unattended, unmanaged.. you had an idea or a problem you ping people around that know that domain, chat around and make a thing. In groups it might turn diminishing returns into a massive life enhancement (in theory, I never worked in such an environment).<p>ps: I actually think that picking this kind of projects is a tiny art. Don&#x27;t scratch all itches but know that knowing is always a good thing.

That&#x27;s the Pareto principle [0]: 80% of the effects come from roughly 20% of the causes (or effort, in this case).<p>Very hand-wavy but I think that&#x27;s also the reason things like expertise exhibit a power law distribution - if as you progress each &quot;unit&quot; of improvement requires 4x the effort of the previous &quot;unit&quot;, it makes sense that only about 1&#x2F;4th of people will make it through. Of course that&#x27;s very oversimplified but I think you get the gist.<p>[0] <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Pareto_principle" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Pareto_principle</a>

As it is with many things this is both right and wrong depending on how you look at it.<p>Consider something like Brazilian Jiu Jitsu. The first 1000 hours will surely advance your game percentage-wise way more than the 1000 hours you accomplish after you&#x27;ve put 10k hours in.<p>However, there aren&#x27;t many people with 10k of bjj practice and you&#x27;re no longer in the rookie world. That 1k may make you just 1% better but that 1% means a lot among the elite.

Centering a button with css should not take two days. If you haven&#x27;t solved the problem already, feel free to contact me and I&#x27;ll be happy to help.

There are diminishing returns in everything because we focus on high impact things first. It&#x27;s not a bug, it&#x27;s a feature.

I don&#x27;t feel like this applies to UX. The third or fourth pass in this area can often make a huge difference.

It might not net you a 7-pack, but it could possibly net you an 8-pack.

Oh, how many hours of my life have I wasted trying to center align. Sad and all too true.