Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

But they left something to build upon.

This is key, regardless of whether you think that "doing it right the first time" would have not taken meaningfully longer, and paid off in the long run over and over.

For any meaningful product, you want to get customer feedback early and often, and you want to do it before your competitors get a chance to.

I say this as a more stereotypically "Process" person/developer than a "Pioneer". I know too many failure scenarios. I overthink. I get into analysis paralysis when there is an open page. I need that Pioneer to help my company and my team get started.

But give me an existing system, and I'll mold it and expand it as quickly as that 10x Pioneer.

I love taking shipped hacked together code, and gradually refactoring it and improving it for 10x, 100x scalability of both system throughput and development team growth.

The important factor here is shipped. In production, with customers. Customers who already see the value and benefit, and don't mind the occasional blips and glitches that will take much longer to fix (and probably require massive rewrites) to fix behind the scenes.

Beautiful code without users is worse than nothing at all.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: