[nineteen999]

We didn't even have to offshore for lots of bad code to be written.

Looks at the scores of Ycombinator startups that wrote a shitload of awful code and failed. Good ideas, pretty websites, but not a lot of substance under the hood. The VC gathering aspect and online kudos was way more important to them than actually producing good code and a reliable product that would stand the test of time.

Pretty much the most detestable section of the HN community. IMNHSO. I notice they're much quieter than usual since the whole vibe coding thing kicked off.

[MrDarcy]

> Looks at the scores of Ycombinator startups that wrote a shitload of awful code and failed.

This can also be restated as, look at all the startups that wrote a shitload of awful code and succeeded.

That’s an indicator code quality doesn’t matter at macro scales. We already knew this though even if we didn’t explicitly say it. It’s more about organization, coordination, and execution than code.

[strken]

This seems like it's reading too much into things. I'm sure driving an ambulance slower vs faster doesn't make a difference to survival in most cases, but on the margins it absolutely does.

Startups are also quite different from ambulances; surviving and minimising patient harm isn't the most important thing for a startup. Instead, it's building a profitable and valuable business. You're not just worrying about the margins, you're also hoping to squeeze out every bit of growth you can.

[MrDarcy]

My statement applies equally to startups and nasdaq 100 enterprises alike.

I’m not following this ambulance analogy.

[rapind]

> That’s an indicator code quality doesn’t matter at macro scales.

I think it can though. It just depends. Having high quality code and making good technical choices can matter in many ways. From improving performance (massively) and correctness, to attracting great talent. Jane Street and WhatsApp come to mind, maybe Discord too. Just like great design will attract great designers.

I also think it might matter even more in the age of AI Agents. Most of my time now is spent reviewing code instead of writing code, and that makes me a huge bottleneck. So the best way to optimize is to make the code more readable and having good automated checks to reduce the amount of work I need to do, like static types, no nulls, compilation, automated tests, secondary agent reviews, etc.

[tikhonj]

I mean, look at all the startups that succeeded despite being complete shitshows behind the scenes... the baseline for leadership, organization, coordination or, hell, execution for a startup to succeed isn't exactly high either.

[mattmanser]

They left ages ago, around the time PH got big.

I can't remember the last time I saw a '10 ways to fit 25 hours in 24 hours' type article on here, which were rife 10 years ago.

[inigyou]

What's PH?

[re-thc]

Product Hunt (I assume)

[rustystump]

I think it is a misnomer to attribute startup failure to bad code. There are so many other factors at play that are more powerful.

Not to say the crowd u speak of doesn’t exist, they do.

[bluGill]

Bad code is one possible axis - not a likely one at that stage though. Bad code gets you a few years down the line when competitors are moving faster than you to the point where they are cheaper and better.