p0rkbelly

There is the problem of literal style though. The aesthetics of say clothes do evolve overtime, not year to year big changes, but every 3-5? Sure. Just laughing at the thought of the model where any image generated is say stuck in 1990s grunge attire.

The second paragraph discusses that BDT is an internal team at Amazon Retail. They used AWS and Ray to do this.

Any insight of when the final action date when F2B -family sponsored Visas may move? Been stagnant for years and I'm one month off...

It would be nice if things only broke during "business" hours and didn't have real world impact. Nevermind impact millions of people around the world. But if you look at the customers of say code that is running cloud infrastructure it is running airlines reservations/checkins, government workloads, banks, hospitals, critical infrastructure, netflix, gaming services. That's a lot of things that can't typically wait for morning.

yeah...different story now. The target comp numbers ) assume 15% stock growth per year from when it's allocated to you. That model is now broke for the first time in a decade+. How it gets fixed... I'm not sure, but, there is history of cash payments to compensate.

Point being, if you're not making more in year 3 than year 2 -- something is broke and/or your manager wasn't supporting you appropriately, or not hitting high enough on the performance ladder.

It's all about the RSUs. That all kicks in after year 2. If you're a lower level maybe you don't feel it as much. But for a high performing L6+ RSUs typically are -- or at least were designed to be -- the majority of your income compared to base pay.

If your code breaks something, you should fix that code. Who else should?

If your system/product/service is down because you have a dependency on something that broke -- well it's up to that team to fix their code.

If you write code at Amazon you also are responsible for the availability of your service. So, you rotate in as an on-call.

There is no central SRE teams, SysAdmins, etc. There is no throwing it over the fence.

There is nobody better to fix a production issue than the person who wrote the code which broke. Plus, you are more motivated to write better code.

OLR is employee performance reviews.

PSA: In exposures like this, Contact the cloud provider too. They tend to have the right contacts for customers. And I'm guessing there are actions they can take as well.

You assume they have a security team :)

This has nothing to do with MSFT or AMZN. A good CTO is at any company provides an example of what to aspire to become. They are mentors and teachers to the technical community as a whole.