tjdetwiler

Amazon actually tells employees that they have a "total compensation" philosophy, which means that when the value of unvested shares increases then Amazon will take that into account when issuing new grants (ex: as part of the performance review and compensation process).

For example, if Amazon thinks you should be paid $250k per year and your total comp for the next year is at $300k based on the value of your granted but not yet vested stock awards, then Amazon will not award anymore stock awards to vest in that year. This is different from most other companies that usually just give you a stock award with a standard vest schedule (ex: 25% vest over 4 years).

Amazon has justified this buy telling employees that if the stock drops below your TC target, then they'll award more shares to make you whole. So the question is are employees going to be down from their TC target, or from an inflated compensation number from during the pandemic when many employees were likely making more than their TC targets.

At least this was how it worked when I was employed at Amazon in around 2017.

You can still return the str reference; callers can easily do the copy if they need while allowing for zero-copy for simpler usages.

With x you're just bringing a window manager that plugs into the x-server. With wayland there's no standard 'window manager' plugin to arbitrary wayland servers. So the wayland example is doing more things (lots is handled by wlroots though).

It sounds like they're actually saying they see Linux as a conduit for cheating and they don't see enough upside to be worth that risk.

CS tools should require some 2FA based on personal information. CS agents should not be able to access arbitrary data.

git config --global core.editor <EDITOR>

Lyft (as far as I know) won't show the driver your destination until the ride is started. It's intended to save time in allowing the driver to bring up directions and not as a decision point for them to decide if they want to take the ride or not.

The email I received made me look at some long lost repositories of mine that I did while learning in school. It's always fun to be able to look back on work you did when you were less experienced.

It's unfortunate how transient the internet can be. How much information is created and lost over such a short period of time.

All APIs have performance SLAs that are not consistent. You may have 50% of requests finish in 200ms or less, 90% finish in 300ms or less, and 99% finish in 600ms or less. You can do work to narrow the performance variation but performance is a % chance.

I personally find cubes to be the worst combination of collaboration vs privacy. You still have people who will walk up to you when you're working, but the cubes really break up the space.

In my office, they have small "conference rooms" which really only have space for 2-3 people that you can reserve if you want to hide away in somewhere quite. I usually fall back to these if I need to go heads down on something.

The best part of the office is the ability to close/lock the door to prevent the annoying "walk ups" that really disrupt work.

I went from private office to open floor plan when I switched jobs last. It was towards the bottom of things I cared about when I was considering the move.

Private offices are definitely nice, but I also enjoy the positives of an open office