The pay for outside working hours applies whether or not you are getting paged. That's 128 hours / 3 = 42.67 hours of extra pay during an on call week. The on call week also gives incentive to fix technical debt and build a more stable production system so you don't get paged.

Yeah, makes sense. Forgot the detail that most of on call hours are not strictly working. So Google scheme seems fair

Waiting to work is working. Would a hospital surgeon only charge for time holding a knife? Don’t be absurd.

Spent years taking oncall shifts. Nah, it really isn't. The two things I couldn't do were see a movie and go hike.

Otherwise life as normal. Laptop in the car, 4g hotspot on my phone. Only actually had to fix an issue remotely a few times (once with only my phone in a restaurant after a martial arts class).

Hospitals do not pay more than normal work hours for on-call, though they do usually pay some amount.

https://physiciansthrive.com/physician-compensation/on-call-...

If I'm at home cooking dinner, I'm not "waiting to work" though.

Yes, you cannot go on a hike, which is why you get paid. You don't get paid more than you do for your normal time working though.

Hospitals are probably one of the places uses on-call the most. A nurse or surgeon on-call doesn't sit around the hospital (at least not where I am from). They sit at home watching TV or eating dinner with friends, knowing that if there is an emergency, they have to go to work.

So they are paid for being available at a diminished rate, and if their availability is needed, then they are paid overtime.

Absurd analogy. My point is that I think it’s fair to pay less than regular hour pay when you are “waiting to work”. I also think it’s fair to pay more than regular hour pay when you are working outside of regular working hours.

We had the same experience as well. When lockdown started, we did a couple of Instacart orders and recommended it to people, until I found out about the stacked charges. If it was just a delivery fee + tip, I'm fine with that, even a transparent fixed percentage. The deception and realizing how much the per-item surcharge + delivery fee + tip was coming out to made me stop using them. Recently I've been using curb-side pickup from stores and its surprisingly convenient and no cost associated. The store workers even refused the cash tip I offered when they came to the car!

They’re not allowed to take tips and are paid garbage wages. Don’t get too excited.

This reminds me of a time I pulled a near all nighter for a final. I came into the final on too little sleep and even though I knew the material, I couldn't think during the test. I took a 20 minute nap during the two hour final, woke up and aced the final.

An async method can use await within it. A method can return a future but not be able to use the await keyword.

What is the point of this restriction? Why not just allow all Future-returning functions to use await?

Async methods also allow you to return values which will be returned as futures.

For example:

  return 4;

If the function is marked async, the return value should be Future<int>.

If you allow a non-async method use await, you get into this situation:

  Future<int> foo(){
    int result = await something ();
    // How to return "result" and still make compiler happy?
  }

Why not just some generic function T -> Future<T>?

It sounds like the async keyword allows for a particular implicit type conversion within the function body, but on return statements only. That's a pretty thin justification for a keyword.

Risk of wasting time, upside of having fun and learning.

They just addressed this in today's announcement:

As for new Flutter features, Google today announced ‘Add to App,’ a new feature that makes it easier for developers to slowly add Flutter code to existing apps. In its early days, Flutter’s focus was squarely on building new apps from scratch, but as it has grown in popularity, developers now want to use it for parts of their existing applications as they modernize them.

This looks awesome and obvious in hindsight, but as patio11 would say, you need to charge more. Especially on the higher end, let people that want to pay more, pay more.

Out of curiosity, which fund would that be?

Great work on launching this and levels.fyi. How does comp.fyi ensure freshness of salary data?

I feel like sites like Glassdoor became a victim of their own success. It became the salary site for years, so naturally it accumulated data going back years. Last I checked, their salary numbers are significantly lower than current industry comp since it has been going up over the past few years and it seems like they don't drop old data from the averages.

Thanks! Definitely a problem even for us. Right now, we're focusing on getting as many people to contribute as possible (over at http://levels.fyi/addcomp.html). We've tossed some ideas around about only showing / averaging the last 10 salaries submitted for a certain company and level and ensuring some minimum date of submission. Glassdoor also suffers from not having granularity of level for engineers and I think that may be why salary data is so broadly ranged.

Why not show recent aggregates alongside overall aggregates?

Yeah you're right, could do both

A graph would be great.