The amount of closeted racism and blind defense in this comment section while knowing this is the peak represention of our industry makes me ashamed to be an engineer.
It's a very common approach. Telling low performing white men they should blame black people and women for their woes is a soundtrack that resonates well.
Last time I rode Caltrain (late last year) I had my life threatened by some low life who got mad b/c they had been in the bathroom for 5+ stops and an employee had the audacity to knock on the door and tell them to wrap it up and get out (I just happened to be nearby) so there's that aspect of it.
The only way to achieve that level of parallelism is by not knowing what you are doing or the peoblem space you are working in to begin with and just throwing multiple ill defined queries at agents until something "works". It's sort of a modern infinite monkey theorem if you will.
I'll be moving off a google phone running GrapheneOS to Apple on my next phone refresh because of this, how is this not Google shooting themselves in the foot?
GrapheneOS is doing well and has an OEM partnership for devices launching in 2027. The switch to 2 major releases per year applies to both the Android Open Source Project and non-Pixel stock operating systems. Non-Pixel OEMs weren't shipping the quarterly releases but rather at most the yearly ones, usually with massive delays. Google is trying to get them to ship 2 releases per year on time instead. They gave up on getting them to ship 4 releases. It's not clear if the stock Pixel OS will continue having 4 major releases per year, but it's clear that if it does that the 2 other OEMs are meant to ship will have more changes. Bear in mind they only had 1 major release per year until trunk-based quarterly releases began with Android 14 QPR2. Android 16 QPR1 being pushed to AOSP delayed until almost right before Android 16 QPR2 was released to AOSP on launch day, they already came close to implementing the new policy in practice without telling anyone about it. The whole thing appears to be due to massive cost cutting for Android and ChromeOS. Android 16 QPR1 appears to have been delayed for AOSP due to major bugs in the code which they worked around for Pixels.
Everything at Google is going downhill due to cost cutting, not specifically this. It's more of a neutral thing for GrapheneOS than a bad thing since it presents a lot of opportunities too. Google is likely to lose control of Android via antitrust action but whether that ends up better for open source is an open question.
...as a last line of defense. MAC is also a stronger system than DAC to being with, so a lot of places may opt to have it in place anyway for inexperienced/careless/lazy admin mistakes. Sorry you struggled with writing SEL policies, but it's a very valuable tool when you run systems that are exposed to the internet or other hostile environments.
Are you going to reach out to 200 people? I imagine only 1-2 of them can actually significantly advance your career in any meaningful way. Wouldn't your time be better spent cultivating relationships with those 1-2 peole rather than collecting data on 200 people who you're realistically not going to see any return from?
Anecdotely, I’m in the interview pool at my mid size company. Our offer to application ratio is 0.4% with over 7000 applications. We are a fully remote company.
I have personally referred 6 people who I know are qualified. Only two got interviews and no offers.
Hell my offer to referral ratio was 50% at AWS. The job market really sucks right now
I have gotten plenty of value out of the platform - including BigTech companies reaching out to me. One offer I accepted and where I worked for almost four years paying way more working remotely than I could have made locally.
My last two jobs have also come from LinkedIn. Exactly how am i supposed to find remote jobs?
reply