No need to be condescending. People can disagree with you without being technically stupid.
> "SO that's what, a few gigabytes? Takes 30 seconds to download? Then run some stats, get some totals and compare it to your check. What's the problem?"
I think you underestimate the complexity of a database that grows by 20 million records per month, but let's say you solve the technical, computational, and programming issues. It's still a bad idea.
Most of Spotify's customers can open and understand their Spotify payment today. Your customers are not database experts. Most people have rudimentary Excel skills at best. Talk down to them all you want, but they won't know what to do.
So what, they should all hire data analysts? To understand their Spotify invoice?? You know you're using technology wrong when you take something your customers currently understand intuitively, and alter it in a way that requires technology. I understand that you're trying to fix a problem, but you're actually introducing new problems that are far more significant.
Don't let the love of nuance override your customer's experience. That's how you build "perfect" products no one wants.
> I think you underestimate the complexity of a database that grows by 20 million records per month
Why does it need to grow per month? Create a new database each month and archive.
> So what, they should all hire data analysts? To understand their Spotify invoice??
There must be some misunderstanding here. The customer's invoice is for $10 per month regardless of invoice complexity. The record of accounting that goes to the artists is what's being discussed.
It seems very simple to provide a database to artists, then also provide an open source database analyzer that will verify your pay check is accurate.
No need to be condescending. People can disagree with you without being technically stupid.
> "SO that's what, a few gigabytes? Takes 30 seconds to download? Then run some stats, get some totals and compare it to your check. What's the problem?"
I think you underestimate the complexity of a database that grows by 20 million records per month, but let's say you solve the technical, computational, and programming issues. It's still a bad idea.
Most of Spotify's customers can open and understand their Spotify payment today. Your customers are not database experts. Most people have rudimentary Excel skills at best. Talk down to them all you want, but they won't know what to do.
So what, they should all hire data analysts? To understand their Spotify invoice?? You know you're using technology wrong when you take something your customers currently understand intuitively, and alter it in a way that requires technology. I understand that you're trying to fix a problem, but you're actually introducing new problems that are far more significant.
Don't let the love of nuance override your customer's experience. That's how you build "perfect" products no one wants.