131 karma · joined September 14, 2011
There is no fundamental guarantees provided by LLM architecture, so to assert anything of sorts would require manually executing the operation and comparing the results. And why not asserting the correctness is not negligence or fraud?
I am not saying it is impossible, but so far I have not found any explanations that would close this huge gap in logic for me. LLMs themselves "admit" the gap cannot be explained rationaly.
So, Google "backs up" a 128Gb worth of photos on the phone onto 15Gb free storage combined with Gmail and who knows what, completely clogs it (as if it couldn't be predicted) and then has audacity to suggest paying for "extra storage". There is no way in online UI to just delete the whole "backup". And the cherry on top: when you finally get to delete some there is a fine-print - "the selected photos will be deleted from all synced devices". Well, I guess I must be thankful that they at least show this warning. This is what passes as "backup" in Google's parlance these days.
The link is fun :). My kill count was 75.
I was hinting at full impossibility to quantify those problems. Starting with un-define-ability (sorry, English is not my native tongue) of the very term "need" upon which the predicate "the needs of the many outweigh the needs of the few". Maybe that is why I am leaning towards "deontological" resolution of trolley problems, rather than "utilitarian".
As for LLMs, I use them and benefit from them. For fun, and hopefully for profit too. But if I had a lever I could pull to make this tech disappear - I would not hesitate one second, deontology be damned. Even better if smartphones suddenly follow too.
Modern filtering using "AI" and ATS of all kinds is such a loaded dice that I believe an honest randomizing like you described would be a significant improvement for both ends of the funnel. Beyond jokes.
Perfect framing! I was leaning towards "AI Chernobyl" analogy in my predictions, but I think "asbestos" or "fossil fuels" captures its nature much better. May I borrow it? I definitely see the harmful consequences of "AI" exceeding both, however with sad realization that it usefulness was absolutely below par with any.
I agree with many, pointing that companies will (try) find ways to fleece any regulation imposed. And I am not a fan of regulations myself, at all. But I think it is fair to hold businesses to some standard in many aspects, including hiring. It is already being done in regards to some, like discrimination and equality. Un- and under-employment is a matter, dealt with by society through institutions and funded by taxpayers. The "clearance rate" of job applications (from both "buy" and "sell" sides) is, therefore, a state concern. I do not think extending requirements of "business license" to demonstrate "genuine intent" would place insurmountable burden on HRs or CEOs. But of course, such extension must have some teeth.
To be clear, the current situation with excessive ghosting is not helped by decades-old push to "commoditize" jobs, particularly IT jobs. And the regulations we discuss will be a not very well-veiled recognition of its de-facto success. Which I am also not a fan of. But flip side seems worse, when companies are allowed to pretend they'd only settle for unicorn while not demonstrating a "unicorn-shaped sieve" at all.
I find it actually extremely useful practice. We engineers tend to center our thoughts around "code" and with such code-centric mindset to accumulate knowledge as "code-adjacent" - in repo's commits, PRs, markdown files of all sorts. But in reality most if not all projects extends past the code, and it makes much more sense to have a "project-centered" mindset. As such, an external "issue" captures much more context and provides more useful insight about project impact than PR description alone. Love or hate JIRA, beyond microscopic solo-projects it makes full sense to use broader-scope external tools for project management.
As a nice cosmetic effect it also removes (some) bickering about whether to put "type" or "scope" first in the commit message :). Simply provide a reference to the ticket! (No, really, I hate JIRA, honestly!)
To my understanding Code Review is first and foremost a trust-building exercise, seeking to establish common understanding behind the piece of code which is to be delivered. That it also may lead to improvements or "catch some bugs" is a distant tertiary side-effect, not the primary goal. At least this is the vantage point I reviewed any code from in the last two decades, and found that team morale and overall quality of teamwork - and delivered software, and customer satisfaction, as a result - responds very well to such interpretation. Regardless of the side you are on and competency level of your vis-a-vis. I would put "elevating competency level of both partners" as a secondary goal of Code Review, and very closely connected to the primary.
With current crop of LLMs there simply nothing on their side to which words "trust" and "understanding" can be meaningfully applied. Hence the "review" takes drastically different shape and implies very different goals. As both the primary and secondary goals described above cannot apply too. The only remaining goal of "improving and bug-catching", in absence of trust, understanding and learning, now requires much more work, which is also much more exhausting.
Agree or disagree with particular foreign policy or military action, why do people forget that the bulk of military is staffed with their fellow citizens? Many of whom aren't terribly privileged to enjoy ample alternative choices to elevate themselves socially or financially. It is exactly this lot who benefits the most from DEI policies, cherished by "pacifists", is it not? It is them who are the first and most massive direct casualties, caused by not having access to the best, superior materiel, doctrine and training on and beyond the battlefield.
I'll be the first to point that military and paramilitary forces attract many with unchecked lust for violence. That "pride", "honor" and "patriotism" are often terribly misused, to uphold goals of those with impure, malicious ambitions. Who, I grant it, also disproportionately represented in the command echelons of military and beyond. But if we are honest, that scum won't be shaken or taught a lesson by SotA technology being withheld from their use or corporation refusing cooperation. It is their subordinates, who, maybe naively, subscribe to "ideal", unquoted interpretation of Pride, Honor and Patriotism, will bear the brunt of being crippled (by the consequences of the withholding and refusal) on the battlefield, and pay with their lives. Don't their lives matter?