It's decidedly inferior in its lack of hubs. If you don't have enough USB-C ports, you're SOL (and given I have a 2-port macbook pro, I feel this acutely).
I have a usb-c monitor connection, and of course the usb-c charger - so any third device requires unplugging one of those. In my case that's a usb-c yubikey. That dongle gives me an hdmi port I can't use (HDMI on the 13" pro can't drive a 34" monitor) and a usb-a port I can't use (I was good and got usb-c perpherals!).
Also, if the stock doesn't perform well, Amazon will grant you more to keep you in the expected band; but it won't take any away if you are making "more than you should".
They won’t take away terms of your existing grant, but they will nerf future annual grants when they see that you’re “already making plenty” with the shares that are yet to vest.
Amazon has a target compensation for you for your first 4 years, with a cash signing bonus making up for the lack of stock in the first two years, so it evens out.
Of course the 5/15/40/40 model only applies to your signing; all further yearly stock grants are over the next 2 years from grant time.
It's common to get a second vesting in your third year (or else your comp would go down). It's almost common to get a promotion around that time -- managers are responsible for promoting their employees, and it's taken seriously.
It also means your destiny is in your manager's hands, which can be unfair if you end up with a bad manager, or several new ones. And unfortunately at Amazon, this is very common (current employee here).
That's literally every job ever. You aren't going to have a successful career at Google if your manager doesn't want you to. The org golden handcuffs are gone, so if you have a bad manager, change teams.
For the record "bad managers" are no more common or less common at Amazon as any other company.
I'm surprised the author didn't consider using DynamoDB Streams to replicate to a PGSQL database for the relational queries while keeping the primary key-value lookups on DDB.
Yep. Non-quorum members can even simply terminate existing connections and refuse new connections from clients, so clients are always either connected to a quorum node or not connected at all (CP, no A)
A notable difference is that Azure file shares have a 5 TB limit for the whole share, and a 1 TB limit on the size of any given file [1], while EFS has no limit on the size of the file system, and a 52 TB limit on the size of any given file. [2]
At least when I started there the first two years had cash bonuses to make up the target-comp difference before the larger stock vests came in, so it was fairly even.
Absolutely, if you stayed, the numbers definitely add up to what you see here. However, because the attrition was so high, you were not likely to stick around to get a bonus to make up for it.
