Hacker News new | ask | show | jobs
by danjac 1910 days ago
“Continuous integration and testing practices" are not exactly a great burden, and you don't know when the thing you are working on is going to snowball and become the thing you need to nurture and grow. Even if you pivot, you will likely want to re-use code written for earlier attempts.

I suspect the reason startups don't do the bare minimum here is because their developers tend to be cheaper and less experienced (at least until they get funding), and "we move fast and break things" is just a lame justification for incompetence.
2 comments
rchaves 1910 days ago
Actually you are more likely to rewrite and migrate away from that legacy codebase once you succeed/pivot

I recommend watching Kent Back’s 3X talk for that, I also wrote a blogpost about it: https://rchavesferna.medium.com/designed-v-evolutionary-code...

link
danjac 1910 days ago
In theory yes, you're supposed to migrate away from the legacy codebase.

In practice I've never, ever, ever seen that happen: it's too much upfront cost to start over, especially when you have real customers and real data on top of it and you need to keep pumping out new features.

link
nabla9 1910 days ago
It's not that. For a startup figuring out what the product is and making it happens in parallel.

Product and product research are the same.

link