[enraged_camel]

I disagree regarding software upgrades.

On the one hand, it is true that unless you have customers, what you have is just a hobby, and you should refrain from stuff that distracts you from solving the core business problem.

On the other hand, certain things become a lot harder and a lot more complicated once you have users, because the stakes are higher. So there is value in making sure you're fully upgraded and patched up before you cross the Rubicon, so to speak.

[threeseed]

I tend to agree with this.

It's easy to do a database migration, library upgrade and breaking changes when you have zero data and zero users. But once you're past that point then even a minor database migration can be a week of work.

[mkong1]

unless you find yourself with an overwhelming number of customers all at once (which would be a nice problem to have), and that upgrade is what would have prevented a problem, trying to keep up-to-date before building the actual product just busy-work.