Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

So, what is it getting at that's not obvious until it's pointed out and you haven't run across before (and how is that related to having a social-sciences background)?

Before app work, unpredictable schedules were a problem for people juggling multiple part-time jobs. Presumably they still are and the news just has a new shiny to play with.

Paying people more to cover undesirable shifts means that people with more flexibility or who choose to make more personal sacrifices will get paid more. I remember something about... pharmacists I think it was? and how these factors lined up with some of the traditional "group X gets paid more than group Y" groupings.

A job that doesn't artificially limit available positions will tend to pay just slightly more than whatever job ranks next for having a wider pool of eligible workers. Something where the next thing in that ranking is panhandling or unemployment is never going to pay well unless prospective workers are turned away.



> Paying people more to cover undesirable shifts means that people with more flexibility or who choose to make more personal sacrifices will get paid more. I remember something about... pharmacists I think it was? and how these factors lined up with some of the traditional "group X gets paid more than group Y" groupings.

This is key because it’s close to the thing that made me go “ah ha” reading the intro: modern surveillance and algorithmically-managed pricing (so, cheaply modified at arbitrarily-fine resolution based on arbitrarily-many quantifiable factors) open up the possibility of pushing this exact effect from groups of workers to individual workers.

You can avoid (at least to some degree not previously achievable) addressing a pool of workers and instead only clear the rate for a particular worker. No human management input needed per-decision or in any part of the broader offer-decision process and surrounding data gathering and measuring, which is what makes it possible.


This is a topic my friends and I have been talking about since at least 2018, and much of this review just feels affirming. It's good to know 4 bozos in Wisconsin aren't the only ones realizing life sucks for Uber drivers. All I can really do about it is vote.

The thing that stood out to me the most is the transparency argument. When you get paid hourly, you're told upfront how much extra you get paid for overtime, for odd hours, etc. But with rideshare apps, a number just shows up on your screen. You have no knowledge of why that number is what it is.

There's also the social side of the transparency issue. Back when I worked foodservice, I could just ask my coworker what they got paid per hour. As a rideshare driver, you never see your coworkers. Even if you did, you have nothing to compare. There's no "per hour," and "per mile" is rife with caveats, assuming the app even shows you that. With no way to compare to each other, how do rideshare drivers collectively discern what is or isn't fair pay?


Great app idea for the bright minds of HN: an app that lets a rideshare driver easily record hour + mileage when working, combines it with the daily earnings (to get $/hr and $/mile) and let's them share with fellow workers.


In dumb people terms, corporate gig economy players are using algorithms to artificially depress wages of random workers for work that is very similar in scope, if not the exact same (they work similar hours, in a similar area, with similar vehicles and in some cases they are even getting offers for the exact same job with wildly varying wages)


It’s like how a normal person who’s worked with a couple of solo independent contractors (say, for some work on their house) and has a sense of how they both price things from past bids, might offer a job they need done by a certain time to both of them—exact same job—at different rates, all else being equal (the homeowner rates their work as comparable), just because they know one of them historically bids lower. They’d prefer the cheaper one, but are willing to pay either rate, and need the job done by time X, so offer it to both, first to accept gets it.

Now throw in a bunch more factors than just prior bid history, thousands of workers in the dataset instead of two, and such high volume and pace of work that you can afford to periodically experiment by setting, say, a random 10% of each set of offer-receivers lower than your formula would usually suggest, to see if anything’s changed and maybe they’re more-desperate for some reason (you don’t even need to know why… though, imagine if you could spot reasons some workers might be more desperate! Hm…)

Now (maybe) extrapolate to similar, slower-paced efforts in less-marginal areas of work. Interesting (yikes) possibilities.


No, like, this is fucking different. Read the damn article. Like, get down to pages 42-46. I know it's a lot to read, it's a law review article, it's fine if you don't read it, but like "oh what is it getting at?" is something that you have to read the article to see.

So like, before the gig economy, yes, you might be juggling a job at McDonald's with another at Jo-Ann with a hardware store, and Jo-Ann called up at 7 and said you have to come in Or Else, and then you came in by 7:45 and they said "eh too many people showed up, nevermind" and you're up shit creek, so now you're poking by your McD's which could always use some extra help with the breakfast rush but wants you to clock out between 10:30 and 11:30 so you're having to call up the hardware store to see if you can get paid there.

That is bad, to be sure. You have to be playing all the angles, checking in with everybody, you have to hustle hard to make ends meet.

But according to this, your job at GigBurger is one where they say "hey if you can work for at least 6 hours today, we'll give you a big bonus," with the caveat that you are auto-clocked-out not just at 10:30 but whenever there's nobody in the checkout line or drive-thru, so that "6 hours minimum wage" has to be accumulated over 10 actual hours at work -- which is fine if you can get that bonus. But the shitty algorithmic part is that when you get the GigBurger App to rack up 5 hours of work, suddenly it says "oh shoot we're overbooked for your current GigBurger Restaurant, but you know there's a big surge in customer demand over on the other side of the city, go there and get 2x wages and you'll also make your last 1h for sure" and they are fuckin' lying to you and leading you to other overbooked GigBurgers in the hopes that they can run you back and forth across the city without paying you until they exhaust your desire for that last hour's work that would get you the bonus. And you have to be able to discern between actual surges and algorithmic lying to determine whether to attempt the journey across the city or just stay put and see if the GigBurger next door has someone clock out early.

The article clearly lays out why this is a difference in quality, not just quantity: it says that the default American story of "hard work and hustle will be rewarded", which you absolutely had in the "unpredictable schedules" world that you are talking about, shifts to one where the psychological story is that "GigBurger is a casino, roll the dice and hope to God that you get lucky today." Any individual unpredictable job might have been a casino, but you knew that your employers weren't all in cahoots to deprive you of a promised lucky payoff that was the only thing that made the job sorta worth it.


> and they are fuckin' lying to you and leading you to other overbooked GigBurgers in the hopes that they can run you back and forth across the city without paying you until they exhaust your desire for that last hour's work that would get you the bonus

Doing this intentionally would require an implausible level of abject stupidity on the part of the people doing it. Anyone in a position to do this intentionally also knows that it would in fact be counter-productive.


I don't think it does. That is, the quasicode algorithm looks something like this:

    def fulfill_order(order):
        range = 3 * miles
        surge = 1
        workers = workers_in_range(order.location, range)
        while len(workers) == 0:
            range *= 2
            workers = workers_in_range(order.location, range)
            surge += 1
        if surge > 2:
            initiate_surge_pricing(order.location, surge)
        
        lowest_cost = min(w.cost for w in workers)
        workers = random.shuffle([w for w in workers if w.cost == lowest_cost])
        for w in workers:
            if worker.propose_order(order): 
                return order.assign_worker(worker)

        # if we're still here no worker has accepted the proposal
        order.raise_bonus()
        return defer_retry_order(order)
This does not read as incompetent pseudocode, to me! But it has the crucial problem.

Just to be clear about how the algorithm is lying, once you are near bonus and thus you're not in that lowest_cost bracket, you need an actual prediction of a place where demand is going to outstrip supply. The incentive system is reactive to actual demand and thus hopelessly noisy as a lagging prediction of demand, and it is being broadcast to try to manipulate driver behavior which means it also secretly forecasts a supply spike. So if we take it as 50% that the surge in demand is real and 50% that the added supply doesn't cover the added demand, then your actual number of surges you have to chase across the city is a geometric random variable with p=25%, and geometric random variables have the frustrating property of being memoryless like a good casino is: if you're exhausted after you've failed to make it after chasing 4 surges across the city, the expected number of surges you have to chase to get your bonus is, well, 4 more. And if you're at your wits' end after those 4 more, the expectation is, well, 4 more.


That sounds more like a poorly optimized, buggy and unbalanced algorithm.

Would it be fine if there's an algorithm that was able to more accurately predict that if you go to this location at those hours you would be able to make 1.5x more for the several few hours?

There's no reason an algorithm shouldn't be able to do that.

Or an algorithm where you can specify how many hours you plan to work and then it will provide what it calculates the most optimal path for you to take, where perhaps you can even use a slider to quickly test.


We could only know whether the algorithm is competent or incompetent, if we can see what it is and what it is optimizing for and how is it doing at that. Without transparency into GigBurger, you can't tell.

This was the nice thing about working for an MEP* subcontractor, I got to see the unions and the company teaming up, “look the margins are razor thin, we want to get home safe and make ends meet but not if it starves the company and we're all out of a job in 5-10 years.” And in that environment, every pipefitter could know that the algorithm isn't specifically screwing them over. The unions needed our explicit sign-off that our tech to help them track the status of their projects wasn't gonna be able to be used to track how much time their folks spent in the bathroom on a given day. But try telling Uber that they need a driver's union, see how far you get.

*Mechanical, Electrical, and Plumbing. I don't fully understand the contracts side but basically the general contractor will take a big construction job and the biggest margin, then subcontractors will design and do parts of the actual fabrication and installation.


Would it be fine if this algorithm had to be open source?


>That sounds more like a poorly optimized, buggy and unbalanced algorithm.

An algorithm that intentionally sends you to different stores so you can't rack up the last requisite hour to make the bonus? Really?


What is the evidence that anyone is doing that intentionally?


Intent is immaterial


It's a hypothetical, sheesh. Did you read the comment?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: