Live data from Hacker News

Startup Anti-Patterns

itamarnovick.com

11–20 of 102 posts

Re: Startup Anti-Patterns

#11
Such anti patterns are like Nostradamus’s prophecies - you see a company flopping then curve fit a narrative to justify the antipatterns.

How do I, as a founder, know that I am falling into an anti pattern? I don’t believe it is possible to know. You can only “know” in hindsight and that makes these anti patterns useless.

Re: Startup Anti-Patterns

#12
post #11

Such anti patterns are like Nostradamus’s prophecies - you see a company flopping then curve fit a narrative to justify the antipatterns. How do I, as a founder, know that I am falling into an anti pattern? I don’t believe it is possible to know. You can only “know” in hindsight and that makes these anti patterns useless.

It takes understanding your own impulses and cognitive biases.

https://en.wikipedia.org/wiki/List_of_cognitive_biases

Most people start a small business for tax reasons, and the few lucky loud clowns claiming hyper-scaling BS is sustainable simply disappear within 5 years.

Best advice, answer the simple question "will random people buy this when no one is looking?"... if you have to explain/sell a product/service more than 5 seconds, than that business model likely isn't sustainable.

I also see a lot of smart folks that think they will get paid for excuses... only lawyers, PR, and politicians are in that business. =3

Re: Startup Anti-Patterns

#13

Python is an anti pattern. Nodejs + typescript is superior across almost every dimension other than data science and familiarity. People think it’s apples and oranges but it’s not. Also don’t forget golang too. If your app is Python in the beginning then you’re pretty much locked in. It’s doable, but you’re going to be dealing with a lot of Python specific warts.

A startup is not the code

Re: Startup Anti-Patterns

#14

Python is an anti pattern. Nodejs + typescript is superior across almost every dimension other than data science and familiarity. People think it’s apples and oranges but it’s not. Also don’t forget golang too. If your app is Python in the beginning then you’re pretty much locked in. It’s doable, but you’re going to be dealing with a lot of Python specific warts.

Python is a perfectly fine choice for a tech stack. Just because you don't like something doesn't make it an anti-pattern. NodeJs + TypeScript have tons of warts of their own that you have to deal with as well. Every language does.

Re: Startup Anti-Patterns

#15
Seems like a useful list of things to avoid when running a startup, plus situations where it may not always be a bad thing.

Still, got a few thoughts here:

> if you build it, they will come

This feels like the cause for so many news/media bundling services, akin to Blendle. Loads of people seem to have the thought process "no-one pays for journalism, that's because it's too inconvenient to subscribe seperately, let's bundle it all", but far fewer people actually seem to want such a service.

> Chasing Blue Oceans

This feels like the explanation for the Wii U, despite Nintendo obviously not being a startup of any kind. The Wii was a blue ocean product, and the company clearly thought the same logic could apply to its successor too. Find an idea that didn't have much competition (using a portable screen to control what's going on elsewhere), and use that to attract a new market.

Unfortunately, while the concept worked on a handheld device, it didn't really feel good to use on a larger scale, and the ideas designed for it (usually some sort of asymmetric gameplay experience) just didn't have the appeal that more traditional ones did.

> Boiling the Ocean

This seems really common with crowdfunded products, since if their scope isn't unrealistic as hell beforehand (and if it wants the public's attention and money, it usually is), it certainly is once the stretch goals start being added and the creators start promising everything and the kitchen sink.

Also with video games, as shown by Duke Nukem Forever, Beyond Good & Evil 2, etc.

Re: Startup Anti-Patterns

#16
Is there an N=1 anti-pattern on the list? I built an enterprise platform on a low 6 figure annual contract for my first customer. It’s looking like there are no other customers who desire the same type of platform.

Re: Startup Anti-Patterns

#17

Python is an anti pattern. Nodejs + typescript is superior across almost every dimension other than data science and familiarity. People think it’s apples and oranges but it’s not. Also don’t forget golang too. If your app is Python in the beginning then you’re pretty much locked in. It’s doable, but you’re going to be dealing with a lot of Python specific warts.

Any stack has its own warts.

Re: Startup Anti-Patterns

#18
post #15

Seems like a useful list of things to avoid when running a startup, plus situations where it may not always be a bad thing. Still, got a few thoughts here: > if you build it, they will come This feels like the cause for so many news/media bundling services, akin to Blendle. Loads of people seem to have the thought process "no-one pays for journalism, that's because it's too inconvenient to subscribe seperately, let's…

> This feels like the explanation for the Wii U, despite Nintendo obviously not being a startup of any kind.

This is a particularly interesting example, because they followed up with the Switch, which is, in some ways, the diametric opposite of the Wii U. Arguably, what happened was that they had the right idea that the hybrid TV/handheld format was the right blue ocean play, but the Wii U failed by being TV first and handheld second, instead of handheld first and TV second. You could probably build a whole business strategy course on just this discussion.

Re: Startup Anti-Patterns

#19
post #16

Is there an N=1 anti-pattern on the list? I built an enterprise platform on a low 6 figure annual contract for my first customer. It’s looking like there are no other customers who desire the same type of platform.

Seems to be anti-pattern #4: If you build it, they will come. His description matches yours almost word for word.

> The founders automatically assumed that if they had the vision and one customer wanted it, many others would

https://www.itamarnovick.com/startup-anti-pattern-4-if-you-b...

Re: Startup Anti-Patterns

#20
post #18
post #15

Seems like a useful list of things to avoid when running a startup, plus situations where it may not always be a bad thing. Still, got a few thoughts here: > if you build it, they will come This feels like the cause for so many news/media bundling services, akin to Blendle. Loads of people seem to have the thought process "no-one pays for journalism, that's because it's too inconvenient to subscribe seperately, let's…

> This feels like the explanation for the Wii U, despite Nintendo obviously not being a startup of any kind. This is a particularly interesting example, because they followed up with the Switch, which is, in some ways, the diametric opposite of the Wii U. Arguably, what happened was that they had the right idea that the hybrid TV/handheld format was the right blue ocean play, but the Wii U failed by being TV first an…

That's very true, the Switch feels like an improvement on the Wii U concept in many ways.

Though I feel the other big difference is that the Wii U Gamepad was highly limited in its capabilities. You could play games on it while other people watched TV or used that TV for something else, but you couldn't go beyond that. You still had to be close to the TV for it to function, and that usually meant being in the same room.

The Switch being a hybrid console meant you could take the whole thing outside of the room if others needed the space, or bring it with you to events or places outside of the home. So, it solved all the same problems the Wii U did (playing while others used the TV), but also a ton of more pressing ones (taking the game with you while traveling/leaving the house, playing in other rooms/areas, etc).

Post reply on HN