I think we are in full agreement. Likewise, I am not in charge of any practical matter, and glad I don't have to answer to any moral or physical dilemma.
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.
Wait, what? I thought everyone agrees that modern models post September 2025 (or whenever Opus or whatever 5.6789 was released) do not hallucinate, make things up, contradict themselves and can review their own output into perfection regardless of task, goal or context???? /s
If the life of everyone (all 8 billion people) is improved by tech by some margin (pick the margin - 10%, 1%, 0.1%) at the cost of x people (pick the x - a thousand, a million, a billion) being killed by the same tech - is it still positive or negative? How do you even reason about it?
No, government must not do any such thing. They must back away, as my literacy, curiosity and intelligence is not their business in the slightest. Nobody owes anything to government, especially trust. But if "government" insists on importance of things they communicate, it is absolutely on them to ensure it is calibrated to everyone's profile. And I still am not obliged to trust them. Once a liar always a liar.
That would end exactly at "Harrison Bergeron" world as described by Kurt Vonnegut, would it not? If every perceived advantage would require you to wear a "handicap".
> We should shuffle the pile and throw half of them in the trash. I don’t want to hire unlucky employees
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.
Oh wow, "4851 unique technologies tracked" - isn't it an indictment on fragmentation of the industry? It is laughable what passes as "unique" "technology" these days. I know StackScope didn't start that, but it is still adding oil to the fire hollowing the industry out and leaving people stranded.
Ghosting does much more harm to candidates than the burden to not-ghost does to companies. I'm not going to cry over all "talent acquisition experts" having to do some actual work. Uncertainty that businesses face does not compare to uncertainty that a candidate face after 18 months of unemployment. Ask me how I know.
In trading (of securities) posting an order without intent to execute is considered market manipulation, which is illegal and harshly prosecuted. There is a consideration that change of mind is possible, but you'll have a hell of a lot to prove in such case before authorities let you off.
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.
How do you know that someone is about to lose their computing chops? They waste a paragraph explaining a convoluted roundabout way to answer question "how many months of 93% growth it takes for something to grow 500x" with useless precision. A kid just started with BASIC learns by heart in a week that 512=2^9 :)
And a follow-up to my comment above, as wanted to reply to "create an issue before filing a PR" remark too.
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!)
In my opinion review will always be a bottleneck, in OS as well as in commercial development.
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.
I grant we are - and also to facilitate understanding of one's thinking by other team members. But what I write "between commits" is not any more an evidence of "thinking" or conducive to "understanding" than the NSFW mouse gestures I make or rubbish I am humming to myself.
Indeed, I hear you 100%. It may be painful to watch "your" military engage in wars that are not righteous, from one's perspective. Are there even "righteous" conflicts these days? But short of demand to abolish all state military, what is appropriate way to express one's indignation? Hopefully all can agree that such demand would be insane; but why, then, those "pacifist" performances, which effectively are calls to deprive military of the best weapons, people, thoughts, strategies, are not considered insane?
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?
- A little script that is best described as "symbolic submodule" workflow enabler for git: https://github.com/fontmaniac/symgit. As in "symbolic link" vs "hard link" - where hash tying host repo and pseudo-submodule is not git-generated, which makes "submodule" completely substitutable. For the description of creation process see the relevant section of Readme.md
- Companion script named Dr.Emmett - to retrospectively time-walk git commit history and rebuild the repo in a new place. It is not opened yet, and may not be ever as it doesn't satisfy LLM/human ratio worthy of publishing.
- Both scripts were made in service to my FNA-"game" project VibeSopwith: https://github.com/fontmaniac/VibeSopwith.Game. A more or less comprehensive description, and treatise on my stance about vibe- and agentic-coding can be found in the project's Readme.md
- VibeSopwith catalysed creation (accretion?) of Nage.Strata: https://github.com/fontmaniac/Nage.Strata - "Not-a-game-engine" collection of useful "primitives" for FNA-based game development.
- VibeSopwith Readme.md has notable mention of "Aether Bodybuilder" - a helper tool for visually coupling Aether.Physics2D "bodies" to specific sprite textures. Fully vibe-coded in a couple of hours, and as such won't ever be publicly opened, having LLM/human ration approaching infinity.
Oops... I am deeply sorry, thank you for the heads up! It seems I've myself committed a cardinal sin that I am usually quick to point in others - rushing to reply without comprehending the full message. (Meta-oops: I realized how LLM-ish it sounds. Quick, reboot before my cover is blown!)
I happen to believe that the flaw being discussed IS fundamental and inherent in the design and architecture of LLM - this is why I always put "AI" in scare quotes. I've spoken about it in some of my other comments, namely this https://news.ycombinator.com/item?id=47162553 and to some extent this https://news.ycombinator.com/item?id=48046333. And as you do, I, too, hope that I am wrong about the hype and its eventual clash with reality, but do not hold my breath.
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.