498 karma · joined June 20, 2022
With FOSS, the common desire is to build fix or modify, but frequently non-code explanations are sparse. That's one place where code reading is certainly desirable, and obviously the reverse engineering described.
Oh, and yes, you can be the middleman -- you seem trustworthy, I nominate you for de novo utopia money dude, enjoy your new, absolute power.
It's a kickback sheme too probably, directors collude to clamp hiring to "the cream of the crop" which is basically no one, while the other 2 outfits benefit from monopsony and an influx of cheaper talent they can make investments until their own situation gets dire, and let hiring breathe again. A sort of autoeconomic career cycle dysplasia.
Most of these jobs are only open if you went to college, decided 2 years in that you wanted to work at one of these joints, worked in a lab for 4 years to get your masters, had excellent grades, and your PI was a friend of a friend.
HR just assumes like 99% of the population is deranged.
See, it's a vicious cycle, the aggressive M&A strategy leads to a need to increase sales, which leads to a larger marketing budget, which finally trickles down in to the price. Now price is actually segmented itself, in terms of up-front elasticity and "walled-garden" elasticity, which Apple can monitor independently of device sales through marketing novelty through the app store and seeing if the nibbles are elastic onto services, say like Apple+. Historically they also have segmented product (XR, Pro XR) to get more data points for the degree of price elasticity, which is probably most responsive because they're the most expensive thing on the broad market.
If FOV at that resolution is a normal book, like 5-10° it's on par with like, a Kindle.
Now in a given position you may not have appropriate communications skills (or missed a memo, intent, constraint) but if you keep your criticisms objective and organized, this probably isn't a trap.
Leveraging some hard to address criticism in a public setting, too late, and viciously is very different from a timely, short, semi-private email. It's rule 1 of communication: know your audience.
+ Safe and Effective Systems
-> What should be expected of automated systems
--> Risk identification and mitigation
What they should really be focusing on is Hazard/Reliability engineering. "Risk" is too broad of a term for safety because it includes "economic harm" which ... well it's by decree. + Algorithmic Discrimination Protections
The only task these system perform is discrimination, and it's impossible to tell what the system can infer -- the Federal government will do anything to avoid naming the root causes of harmful inequality experienced by protected classes (and addressing that instead of holding a butter knife up to the neck of a shiny object). + Data Privacy
This is actually impossible without trust. Homomorphic encryption isn't a thing. This isn't happening. + Notice and Explanation
-> Why this principle is important
Chicago kept a secret watch list of violence-prone individuals. https://chicago.suntimes.com/2017/5/18/18386116/a-look-insid... is this important? If it was derived from OSINT, and it was being used for public safety purposes why is the federal government meddling in it -- do they have a monopoly on secrets? They shouldn't, if the public safety of Chicago is to be seen.edit: I'm not sure what the criticism is here in light of the Notice and Explanation requirement -- there was N&E at most 4y after the practice began -- and it wasn't really a gaffe, presumably such a risk assessment system is still being used. I guess the argument is that this should have been required, or made earlier?
+ Human Alternatives, Consideration, and Fallback
This is probably what we need more of at first, and then less of later -- once all these goofy flat "simple" decision models have been replaced.Here's a clear drawing of the ideal system without all the pesky words: https://ibb.co/7KrgBk4
unsafe
parts are GPLed.AMD and Nvidia sell the same thing made at the same place in Taiwan.
Nvidia dove in like 1998. AMD sold it's moat in like, 2005.
A spacecraft isn't an aircraft.
"Take 3 hours of floor arguments and committee testimony, and identify compromises."