redthrowaway
What's interesting to me is not the above, which is naughty in the anglosphere, but the question of the unknown unknowns that could be as bad or worse in other cultural contexts. There are probably enough people of Indian descent involved in GPT's development that they could guide it past some of the caste landmines, but what about a country like Turkey? We know they have massive internal divisions, but do we know what would exacerbate them and how to avoid them? What about Iran, or South Africa, or Brazil?
We RLHF the piss out of LLMs to ensure they don't say things that make white college graduates in San Francisco ornery, but I'd suggest the much greater risk lies in accidentally spawning scissor statements in cultures you don't know how to begin to parse to figure out what to avoid.
Please tell me you held onto your stock
$ npm list --depth=0
<removed for opsec>
├── @babel/[email protected]
├── @babel/[email protected]
├── @graphql-codegen/[email protected] extraneous
├── @graphql-codegen/[email protected]
├── @graphql-codegen/[email protected]
├── @graphql-codegen/[email protected]
├── @graphql-codegen/[email protected]
├── @graphql-toolkit/[email protected]
├── @graphql-toolkit/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @types/[email protected]
├── @zeit/[email protected]
├── @zeit/[email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── UNMET PEER DEPENDENCY [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── UNMET PEER DEPENDENCY [email protected] - 3
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected] $ time rm -rf node_modules/
real 1m2.969s
user 0m0.409s
sys 0m15.853sAttacking SSL VPN: PreAuth RCE on Palo Alto GlobalProtect, with Uber as PoC
But then the moonshots quietly end. Boeing makes cost effective tweaks to its current lineup, and lands fat defence contracts that pad the bottom line and drive the stock to stratospheric prices. It gets comfortable, it gets efficient, and it stops being what made it great in the first place.
Apple post-Jobs will likely be an extremely profitable company for many years to come. But it will never again be the pioneering company that forged whole markets from vision and belief.
And that's sad.
Cookies have been around for 25 years and are dead simple, and Brussels failed spectacularly to understand, let alone sensibly regulate, them. Colour me skeptical they'll manage to wrangle something that even the people working on it barely understand, and that's changing on a yearly basis.
Ask HN: How do I become a better team lead for a small, junior dev team?
I'm a senior developer at a small startup managing a team of three co-ops and one junior dev. My team members are great: eager, smart, curious, and effective. I rarely have to teach them how to solve a problem; they naturally research and implement solutions.But I didn't get a CS degree because I'm great with people. I've had some limited management experience, mostly interviewing applicants...
They may not want to sign the letter simply because they're offended by singling out China for opprobrium.
Elon brings incredible value to his companies. He also brings incredible risk. The error his fans make is in assuming the two are inseparable--that you can't have the space visionary without the libel, or the automotive and energy revolutionary without the fraud.
I think this is a mistake. You could solve most of Elon's problems by giving someone the ability to preview his tweets before he sends them. I can't see how putting a broadcast delay on his twitter feed would stop him from building cars and rockets.
Giving Mars a Magnetosphere
Those little social buttons that track every user and nobody ever clicks? You're going to have to spend as much time making the case to your boss why they're a bad idea as you would simply implementing them. Ditto ad spam, interstitials, sticky banners, and the like. And if the UX is bad but conversions increase, good luck.
These sorts of guidelines are great for small sites you control yourself. The chances of being able to follow them, even if you give a shit, on a corporate site where conversions put food on the table, is essentially nil.
Also, the diminishment of the back catalogue (and the fact that so much of it is SD--not their fault) is negating one of their biggest selling points.