News for hackers. Stuff that matters.

adanhn

Re:The Case for Location-Independent Salaries on Saturday July 24, 2021 @12:39PM (#27942345)
At my former job, we lost excellent team members because of location-based pay adjustments, and it hurt every time. The person would decide to move to a different city (or country), they’d be told they were getting a pay cut, and they’d look for (and find) a new job instead. Often they wouldn’t even bother negotiating. I can’t blame them, it’s just rough, even a little humiliating.

When you have an employee who is performing well and wants to move cities and you cut their pay, you’re basically telling them one or more of: - I don’t trust that you’ll do a good job remotely/in your new location/timezone, so I’ll pay you less. - I value remote work less than in person, so I’ll pay you less. - I am paying less or intend to pay less in the future people in your new location, so I have to pay you less too so that it’s “fair” to the other employees in that location.

In short, you’re giving the employee an really big push to shop around for other jobs, and that never ends well for the company. As an employer, why take the risk?

And that’s looking at the case of an existing employee who is moving. But even with new hires, I’ve been told all kinds of bogus reasons for why it’s the best (or only!) system, when there is only one reason, and that is saving money. Same reason companies have their customer support in Philippines or their sneaker factories in East Asia. Leveraging differences in market prices in a global environment. But it’s just cold economics, it has nothing to do with fairness.

My favorite bit of knowledge here is that you can migrate before you must, which means that you can choose the timing, the process, and spend time doing as much testing as needed.
> We have webhooks that are like Apple's server-to-server notifications, but not terrible.

That made me chuckle. Sounds like event webhooks + ETL exports should cover everything. So far Apple's metrics have not only been very limited, but the fact that we can't relate them to our user data means that they're almost useless. You can't segment by demographics, correlate to the user's history (are people who do X more likely to convert?), you can't even a/b test.

Any company that is on the AppStore and takes themselves seriously needs to know what they're making off each individual user to the penny. If RevenueCat helps with that, then I expect you'll do very well.

About time. It just saddens me that after so long dealing with the myriad problems of selling through the AppStore, the response has to come from a third party instead of Apple. Well, I guess it's developers solving developers' problems.

Question: How does RevenueCat data integrate with my data pipeline? Seeing all the metrics and charts in your dashboard is great, but if I already have a data solution set up, is there a way to export all the revenue data from RevenueCat into our infrastructure?