While hourly rates seem like an easy way to get a quick fix for a problem, getting paid for fixing issues creates an incentive to create more buggy software.
Read here for a comparison between the two models!

· Moa · 1 · 3 · 7

@nextcloud This feels like a justification, rather than an actual analysis. The claim that you'd earn more if you made more bugs could be countered by saying that nobody would use nextcloud if it was buggy. The analogy with health insurance isn't bad, but the important distinction is that its the customer who decides in that scenario. If it were the insurance company that decided whether you needed insurance for a cold, I guess they'd say that you do.

@nextcloud I HATE sass, i hate that what once cost me $100 is now $50/ year even though the product is unchanging. That said, this is only really an issue with services like adobe, where my subscription gives me access to the product, (when I stop paying I lose all access). Presumably if your customers stop paying, they keep the code they're running and lose the support. That's fine, support is clearly a service. I think your article could do with a bit more upfront honesty.

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!