I've not worked at Meta, but I was at a similar scale of company for 2 years before being let go. Once you factor in RSUs, they essentially paid double what I've ever made anywhere else. Knowing how volatile those sorts of positions can be, I just saved & invested all the extra, which worked out quite well.
The sun still. It's just that that side never points towards the earth, but it still gets sunlight. Same as how the side we see isn't fully lit except during a full moon.
I'm not at all familiar with the Xbox One, but this is a feature that's generally available if you're designing "closed" hardware like a console. Most SoC these days have some sort of security processor that runs in its own little sandbox and can monitor different things that suggest tampering (e.g. temperatures, rail voltages, discrete tamper I/O) and take a corrective action. That might be as simple as resetting the chip, but often you can do more dramatic things like wiping security keys.
But this exploit shows that it's still almost impossible to protect yourself from motivated attackers with local access. All of that security stuff needs to get initialized by code that the SoC vendor puts in ROM, and if there's an exploit in that, you're hooped.
This attack is on the early models that didn't have those protections enabled. The researcher surmised that later models do indeed have anti-glitching mechanisms enabled.
I've been working 4/10 schedule (4 days, but 10 hours/day, so I still work 40 hours). It's a HUGE perk, and is the biggest thing keeping me at my current job.
Honestly I think the dirty secret is most peoples work output, especially in white collar work, is not linear. I'm willing to bet if you are even able to quantify your output (I don't believe most people can do that unless they are merely a fungible cog in some production process), you'd get the same exact amount of work done in a year working 4 10s or 4 8s or 4 5s I'd even bet.
Think of the classic case of the deadline and what it actually means. Case A, you didn't procrastinate. You took plenty of time to think on the problem, work on a solution at an unhurried pace, put it aside, come back to it, and solve it before it is due. And then, it is done.
Case B, you did procrastinate. You have no time at all to think all day, you immediately do and iterate. Four hours later you've sprinted and delivered. And then, it is done, same as it would have been if you didn't procrastinate, maybe 10 fold reduction in time.
And that is worst case examples. Typical case is probably somewhere between these A and B, but the point is non linear time to output.
Happiest and most productive I've ever been was working 4/10 with a start time at 2 p.m. No morning sluggishness walking into work after lunch, zero-traffic commute, off Fridays so I'd still have a social life far, far away from morning people. Dated a nurse who also worked night shifts and just went on weekday lunch dates or closed down bars.
First time around, luck mostly. Happened to get hired by a company that switched to this schedule. I eventually left for higher pay (but gave up my Fridays). Eventually got laid off, and a friend who was still there managed to get me a spot back on her team. By that time, they'd embraced remote work during Covid and decided to keep it permanently.
Granted, I could probably be making way more if I were to leave - I took a pay cut when I went back the second time. But at this point in my career, I value the 4/10 and lower stress job (no on-call rotation) more.
reply