Hacker News Reader

But who really work like this? The most people and company would not do this extra work and use tailwind for finished products too.

View on HN

I figure most startups would build an MVP in two weeks and then rebuilt it later or move onto the next version and clean it up a bit in each version that follows.

Never change a running system. If you create a working project, you will not change it, especially a startup.

Possible on a later bigger update (if necessary), a complete app would be rebuild. But here is the same problem: why should you do it, if your project works?

I personally had not seen such an update in early stage of a startup. Did somebody have insights or examples?

Agreed, even if you do a rewrite - you'd still want to use tailwind so you can re-use some of the elements you already built

Reply on news.ycombinator.com