Live data from Hacker News

Why my projects keep failing

adayinthelifeof.nl

11–20 of 58 posts

Re: Why my projects keep failing

#11
post #7

The hardest lesson I struggle with is the Pieter Thiel line "the something of somewhere is always the nothing of nowhere". It is easy to see something that can marginally be improved or copied to perfection but this does not give you automatically the customer base and history that made the original work as a business.

> "the something of somewhere is always the nothing of nowhere" Never heard this one, what does it mean?

The parent slightly misquoted it and it really needs the context.

The Silicon Valley of Iowa, is actually the nothing of nowhere. He is saying that when you are using the name of the original place to claim yours is the new place, it's more likely what you've got is a nothing of nowhere (ie the new place really doesn't matter, thus you're attempting to borrow reputation in naming in the form of the Silicon Valley of country/city/location).

The same usually goes for products/services as well. The Uber of XYZ is most likely garbage if that's how you're identifying your service. We're building the Airbnb of lawnmowers. And so on. Thiel's quote is essentially about knock-offs, copying, derivatives and how effective (or not) that process tends to be.

Elaborated quote from Thiel (from seven or eight years ago; may be extracted from his book, Zero to One, in which case it probably actually dates back to the Stanford lectures he did):

"There are a few different problems with it, one is that it is not even clear why Silicon Valley works. It is a singular thing, it is one time, one place. It’s very hard to figure out what are the factors which drive it. Is it the fact that it has good weather? Is it the fact that you have this whole network effect of people and some very successful companies which have been built over years? Is it the unenforceability of non-compete agreements so that employees can leave from one company and go and work in another in the state of California?"

"And then I always think that once you have set out to copy something you have already put yourself in somewhat of an inferior position somehow. The something of somewhere is the nothing of nowhere. The Oxford of Iceland is not Oxford. So all these – Silicon Beach, Silicon Roundabout – these all sound like inferior knockoffs."

"You don’t want to start with an inferior derivative. The question always has to be, what is it that you can do that is better than elsewhere? In the London context, there is a sense that it is the most cosmopolitan city in Europe and that is probably the strength that London should be pushing towards. There has been a lot of interesting finance innovation in London and so that seems natural."

https://www.theguardian.com/business/2015/jan/04/the-innovat...

Re: Why my projects keep failing

#12
post #10

Earlier quoted context omitted.

> "the something of somewhere is always the nothing of nowhere" Never heard this one, what does it mean?

Another way of saying this would be "it is harder to copy something than it is to make something". For example try building a successful search engine today, to beat Google at their own game, you need to solve all this technical problems plus beat a heavily intrenched incumbent. You can point to something like duck duck go and sure they did find a successful niche of privacy aware people that want to "degoogle" their…

This doesn't always hold.. You might argue that google probably aspired to be a yahoo, but I agree itt's bad to market yourself as a konckoff of something else.

Re: Why my projects keep failing

#13
post #3

Almost by definition, most new projects in software are failures. The reasons are simple. 1. Incumbents benefit from network effects in users, and integrations. 2. Due to 1, most software markets consolidate around a top player and a list of 2-10 second-tier players. The top player will hold 90% market share and the remainder will split the ~10%. 3. It costs only slightly more for a top-player to keep staying on top…

It depends what you are trying to achieve but there are usually niche corners of any market which are underserved or ignored by the incumbents. While you may never become the top player in the market you can make a decent living in many of these if you find the right corner of the market.

Of course, if your aim is to become a silicon valley bro living on ramen noodles and angel investor tears then you'll need to find a way of disrupting the incumbent, and if your plan is to do the same thing but cheaper you are wasting your time.

Re: Why my projects keep failing

#15
I engineered my life to keep working on side projects for the rest of it, getting a low stress job with low but decent pay. These are some points I try to keep in mind when making them:

* Inspiration is the most valuable fuel in the universe: Spend some, save some, replentish.

* It's MVPs all the way up: focus on the most important tasks, prioritize the most difficult ones. If that gets done the rest is easier, but don't waste too much time on that.

* Forget about it: Let the project rest in the freezer for a few days. Revisit what the project should accomplish with a clear mind. Use it daily, suffer from bugs and missing features.

* Damn! It isn't what people want: The project might need to be oriented in another very different direction. New features might be required that will eclipse the original idea. It's depressing, but is the idea worth it?

* Get better at sales: and this is the part I'm still working on...

Re: Why my projects keep failing

#17
The definition of success in his terms is insane I think. The bar is set so high. I would consider my side project a success if I get a ugly version running a basic thing that I designed it to do! By projects he mean actual companies/hard problems. Maybe a person who is good with highly talented people can get some success in a partnership!

Re: Why my projects keep failing

#18
Great to see this post on HN front page. Joshua is a technical inspirational guy. I was lucky to meet him several times when he organised meet-ups in Apeldoorn. The problem mentioned is typical for most self employed engineers. Creating a sustainable business requires many years of dedication to just one idea imho. It’s never about the software that is part of the product. But it’s all about the problem your product solves for your customers. Creating a sustainable businesses based on an innovative software product is still not a hard scientific science. But using Problem Solving Methods (PSMs) is key for solving complex problems like creating a viable business. See e.g. https://www.bm-support.org/problem-solving-methods/ for some approaches.

Re: Why my projects keep failing

#20
This is great. I love it when there’s honest post from a builder.

The explanation for failure is clear to me. None of these products as they are constructed are customer-lead. They don’t start with product market fit. As crazy as it hounds the number one reason startups fail is a lack of customers.

You love building the technical solution. You want to have market success.

But your passion is probably not talking to the customer, gathering requirements, or doing promotional talks and webinars.

You need a product or marketing focused partner to handle that side of things. I’ve always looked at the ideal team as being three roles: ops, product and maker. The details, the customer and requirements and the build team each are critical to getting product market fit and that’s just everything when it comes to this stuff. I would just focus on finding a partner in crime because your are obviously a wonderfully talented engineer.

Post reply on HN