We Rewrote Everything in $hotlang, and Our Startup Still Failed
11–20 of 41 posts
Re: We Rewrote Everything in $hotlang, and Our Startup Still Failed
#12I've found: - amazing business running on ball of mud code maintained in an insane way - the perfect architecture, CI/CD, TDD where the business/product has little/no value for the customer Also, I've seen the same stacks succeed and fail. The only common thing I can see is: - when the tech team fully understand the stack they're using - when the tech team fully understand the product and business they're building (a…
Shoddy architecture and even a bad product can be compensated by marketing, hype or a good sales team, while the most pristine architecture and codebase will not help you at all without any customers.
We technologists often focus on the technical aspects, but in many domains they are the least important part for a startup.
Re: We Rewrote Everything in $hotlang, and Our Startup Still Failed
#13I've found: - amazing business running on ball of mud code maintained in an insane way - the perfect architecture, CI/CD, TDD where the business/product has little/no value for the customer Also, I've seen the same stacks succeed and fail. The only common thing I can see is: - when the tech team fully understand the stack they're using - when the tech team fully understand the product and business they're building (a…
Re: We Rewrote Everything in $hotlang, and Our Startup Still Failed
#14Later in the post:
> Had we had more funding, we would have taken the time to rewrite our app in $ELITELANG instead. Our startup could have been a unicorn.
Although this is satire, it's something a lot of funded startups do. They think they've solved user acquisition by getting investors money (hey, let's throw a couple thousands at Google/FB Ads, although there are 15+ viable acquisition channels we could try [1]), and spend time on building things in their own bubble.
Also, the launch mention is pretty accurate:
> We launched v2 of our product with a splash.
Wonder if many startups would have better results if flipped the switch and treated product creation as a "launch" (a bunch of big sprints with a deadline) and user acquisition as something they do steadily, over a period of time.
[1] https://zerotousers.substack.com/p/15-acquisition-channels-i...
Re: We Rewrote Everything in $hotlang, and Our Startup Still Failed
#15I've found: - amazing business running on ball of mud code maintained in an insane way - the perfect architecture, CI/CD, TDD where the business/product has little/no value for the customer Also, I've seen the same stacks succeed and fail. The only common thing I can see is: - when the tech team fully understand the stack they're using - when the tech team fully understand the product and business they're building (a…
I have seen the same, but came away with a different conclusion. Shoddy architecture and even a bad product can be compensated by marketing, hype or a good sales team, while the most pristine architecture and codebase will not help you at all without any customers. We technologists often focus on the technical aspects, but in many domains they are the least important part for a startup.
It is true that having a nice tech stack can make doing your thing easier, but it can also distract you from doing your thing well.
Re: We Rewrote Everything in $hotlang, and Our Startup Still Failed
#16Does this really happen?
Re: We Rewrote Everything in $hotlang, and Our Startup Still Failed
#17Does this really happen?
Re: We Rewrote Everything in $hotlang, and Our Startup Still Failed
#18Re: We Rewrote Everything in $hotlang, and Our Startup Still Failed
#19I think I spotted the error they made. There is no mention of machine learning at all!
Re: We Rewrote Everything in $hotlang, and Our Startup Still Failed
#20This is just a parameterized version of the post from yesterday: https://news.ycombinator.com/item?id=25198571