4,428 karma · joined July 18, 2022
[ my public key: https://keybase.io/logandark; my proof: https://keybase.io/logandark/sigs/m6zjqnGMWscZConP_8q5dTxchLtZC37IPnwlaj0mBGo ]
Even so, I'd argue that you still have to define how to use those abstractions rather than only the result you'd like to achieve with them. Sure, maybe the abstraction has a ".achieve_the_result()" method, and calling that method is how you achieve it, but often there's a bunch of stuff you fit together to achieve a solution to your problem and the compiler doesn't necessarily do that for you.
I think there actually may be some compilers that get closer to this, for example some problems can be expressed quite elegantly in Haskell or APL and the compiler will do a lot of black magic behind the scenes to get you a performant executable (somehow). But for most traditional compilers you are still going to have to define how to approach your problem, even if only at a higher level thanks to libraries.
A common pattern is: gut the company for a fresh start -> have hope for a year or two -> lose hope because you're not seeing profits fast enough and then exit. Microsoft has been known to do this -- remember Nokia?
What a name!
(Skipped the rest of the article cause it's AI.)
I might just not know enough compilers, but didn't you write the specification of how to approach the problem, not just the problem itself?
I don't think we will see Cloudflare enabling an "age assurance" requirement by default. I feel like I could trust them slightly more than a site operator, depending on how it's performed, but I also feel like it would be very easy for them to do much, much worse than any site operator, due to the inherent power of being a GAA. (Global Active Adversary, to those not familiar)
You're right though that the process in practice can be more fuzzy (e.g., you weren't looking, but heard of an attractive opportunity and then applied that way).
I think what's happened here is the inverter does not have its own setting at all, it's controlled by a central computer, which in this case failed.
As much as I've enjoyed the article so far, little LLM-isms like this turn me off just a little bit. It's not egregious but it's somewhat distracting.
(There were some earlier that I glossed over because the article's good enough. Good job to the author for making it relatively painless, but still.)
It gets slightly more LLM-ish towards the end, not to an unacceptable level but still noticeably so. Maybe the article could've been a bit shorter, as most of the best information is earlier.
> In Summary
I also think this entire section is unnecessary, and that it would've been perfectly complete to simply end after "This type of negative response is very rare." Just personal preference though.
"Sorry officer, I didn't drive through a house and kill three innocent people, it was the car that did it. I only turned the steering wheel, but the car was the one to veer off the highway and crash into the building"