Do Things that Don't Scale (2013)

&gt; &quot;Right then, give me your laptop&quot; and set them up on the spot.<p>This article just makes me miss the pre-pandemic times when touching someone else&#x27;s laptop didn&#x27;t feel like a huge health violation.<p>&gt; things that don&#x27;t scale<p>Some things that don&#x27;t scale (i.e. super personal interactions) do have non-linear returns. An email blast can hit 1000 users. But talking to 10 people can generate recommendations. Which hold way more value than marketing emails.<p>I launched a product earlier this year and it has been much harder to get this level of personal interaction over email &#x2F; digital platforms. It&#x27;s a lot easier to ignore an email than someone in the same room.<p>Very excited to return to a world of human &gt; human interactions.

It&#x27;s so hard to put your finger on why exactly this strategy is so important. To illustrate this, consider these two options:<p>1. Your business needs to accomplish X. X is a manual task right now. It could take you 80% of your available time, but you would learn the ins and outs of your business.<p>2. The alternative is to hire someone to do X. Perhaps you could even find someone who is a specialist at X and much better at it than you are. Or you could perhaps focus on postponing X until you&#x27;ve written enough code that you can automate it.<p>Prior to PG&#x27;s essay, the logical thing would have been to recommend the second approach. But today, most HN readers would agree - myself included - that the first approach is the right one. The best explanation I can offer is that building a startup is invariably a learning process, and doing X yourself forces the founder(s) to go through that process early on when the course corrections are cheaper.

In my experience this is the single best essay on how to get to product&#x2F;market fit as a startup. Short read, great examples, killer recommendations. I use it as the starter point for startups and innovation departments that I work with.

I am living through this right now and have asked this questions on several forums because when you&#x27;re really in the midst of this hustle you start to question your priorities and constantly get this feeling about if there is a better way. This is a counter-intuitive advice on building a product and a company but the other option would be to get lucky.<p>Couple of more examples about doing things which don&#x27;t scale:<p>Instacart manually built their product catalog for the first few million products.[0]<p>Pandora analyzing 10,000 songs manually for recommendation. [1]<p>[0] <a href="https:&#x2F;&#x2F;youtu.be&#x2F;uV4lzz1Z0C8" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;uV4lzz1Z0C8</a><p>[1] <a href="https:&#x2F;&#x2F;youtu.be&#x2F;bTtq-M9iDHI" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;bTtq-M9iDHI</a>

Having a small experience of this with a hobby project (an AI-powered chat bot). First versions, for each bot, I just cloned the repo and did a new deploy. That&#x27;s finally become unworkable, so now I&#x27;m converting the project so that one server can handle many bots.<p>Getting to punt on all <i>that</i> overhead definitely helped the initial &quot;launch&quot;, and IMO the code quality. It&#x27;s proving incredibly easy to switch it over, and I think a lot of that is coming from how polished I was able to make the core of it.<p>Reminds me of Factorio: First you spaghetti (shitty probe project), then you mainbus (vertical scaling, haha), then you city block (horizontal scaling).

I like this essay. Another take on &quot;do things that don&#x27;t scale&quot; is in the technical sense that, this is evidence you are actually solving a hard problem. If you limit yourself to only things where the tools to make it wildly successful at scale already exist then you&#x27;re flattering yourself a lot to think nobody every thought of that before and the world is just waiting for you to create it. It is much more reassuring to know that there are hard real world reasons why this problem isn&#x27;t solved yet and you will differentiate yourself by solving them because you actually have some unique advantage, knowledge etc.

I think the important thing highlighted in this article is that a startup needs to do whatever it can to survive - which means its okay to quickly do things that won&#x27;t be sustainable later. A startup needs to hit the ground running, whether that means building a quick MVP or taking to the road for users. If it doesn&#x27;t build a stable position to start off from or focuses too much on planning&#x2F;scaling then it won&#x27;t ever be able to move from square 1. When the startup gains traction and critical mass, then it can start thinking about scaling and long-term performance.

I wonder whether there are any examples not within the startup world but building your own personal “brand” (for want of another word), or competitive edge if that works better.

The wisdom of the article aside, pg&#x27;s web page seems ripe for a redesign...it&#x27;s odd to see the line widths being so narrow in the era of wide HD monitors

I see a pattern:<p>- Someone writes an article with a catchy title.<p>- Someone [semi or quite] influential notices, and says: &quot;Hey, let&#x27;s write an article from the opposing perspective, to be contrarian, and see if we can also make some good points.&quot;<p>- Me: [Doesn&#x27;t click and] thinks &quot;Would ya look at that? An article&#x2F;author which is contrarian probably just to be contratian. I&#x27;m gonna find something else to read...&quot;