It is important to remember that clarifying the legal implications of "pledge" is entirely different than supporting and/or defending this instance of its usage.
One can do the former whilst repudiating the latter and remain logically consistent.
I'm not understanding why clarifying the legal implications is important if it's a smoke screen for everyone involved doing what they are going to do anyway. It seems more like a distraction away from the real problems.
Using Claude to provide a legal definition of "pledge" is unconvincing at best.
> What are the legal protections of a “pledge”?
To answer that question is to first agree upon the legal definition of "pledge":
pledge
v. to deposit personal property as security for a personal
loan of money. If the loan is not repaid when due, the
personal property pledged shall be forfeit to the lender.
The property is known as collateral. To pledge is the same
as to pawn. 2) to promise to do something.[0]
Without careful review of the document signed, it is impossible to verify which form of the above is applicable in this case.
> A pledge is a public commitment or statement of intent, not a binding legal contract.
This very well may be incorrect in this context and serves an exemplar as to why relying upon statistical document generation is not a recommended legal strategy.
No, this is not my goal. My goal was to illuminate that Claude is a product which produces the most statistically relevant content to a prompt submitted therein.
> I'm not sure why your failure to do so should be taken up with law.com?
The post to which I originally replied cited "Claude" as if it were an authoritative source. To which I disagreed and then provided a definition from law.com. Where is my failure?
> Law.com's first definition is inapplicable.
From the article:
The pledge includes a commitment by technology companies to
bring or buy electricity supplies for their datacenters,
either from new power plants or existing plants with
expanded output capacity. It also includes commitments from
big tech to pay for upgrades to power delivery systems and
to enter special electricity rate agreements with utilities.[0]
> That leaves us with the second definition, which says nothing about whether a pledge is legally binding.
To which I originally wrote:
Without careful review of the document signed, it is
impossible to verify which form of the above is applicable
in this case.
Said article is not about a loan backed by a security agreement. That eliminates law.com definition 1.
Law.com definition 2 is silent on whether pledges are binding.
Thus ended your research.
I don't know why you care if Claude.com is authoritative. Law.com isn't either, the authoritative legal references are paywalled. A law dictionary, as we've demonstrated by law.com's second definition's vagueness, isn't necessarily even the correct reference to consult.
Your failure, I suppose, is that you provided worse information than Claude. I suppose you should have typed "Don't cite Claude please" and moved on.
> Your answer is less useful and thought out than the Claude response.
"Less useful" is subjective and I shall not contend. "Less thought out" is laughable as I possess the ability to think and "Claude" does not.
> Claude actually answers the question in the context in which it's being asked.
The LLM-based service generated a statistically relevant document to the prompt given in which you, presumably a human, interpreted said document as being "actually answers the question". This is otherwise known as anthropomorphism[0].
> We need key AI researchers at these companies to speak out ...
See this[0] article from Business Insider dated 2026-02-16 titled:
The art of the squeal
What we can learn from the flood of AI resignation letters
And containing:
This past week brought several additions to the annals of
"Why I quit this incredibly valuable company working on
bleeding-edge tech" letters, including from researchers at
xAI and an op-ed in The New York Times from a departing
OpenAI researcher. Perhaps the most unusual was by Mrinank
Sharma, who was put in charge of Anthropic's Safeguards
Research Team a year ago, and who announced his departure
from what is often considered the more safety-minded of the
leading AI startups.
> It's kind of like the small string optimization you see in C++ ...
Agreed. These types of optimizations can yield significant benefits and are often employed in language standard libraries. For example, the Scala standard library employs an analogous optimization in their Set[0] collection type.
This is the recommendation I have heard peers, both technical and managerial, echo for years in one form or another:
4. Upskill professionally. We're not hiring code monkeys
for $200K-400K TC. We want Engineers who can communicate
business problems into technical requirements. This means
also understanding the industry your company is in, how to
manage up to leadership, and what are the revenue drivers
and cost centers of your employer. Learn how to make a
business case for technical issues. If you cannot
communicate why refactoring your codebase from Python to
Golang would positively impact topline metrics, no one will
prioritize it.
The above involves one thing people can possess which GenAI cannot; understanding stakeholder problems which need to be solved and then doing so.
You seem to have forgotten politics, since at the managerial level that is the most effective tool at hand. Engineers with their arguments and rethoric be damned.
Engineers can make an argument if you can also logically and coherently tie your argument with outcomes that can grow pipeline and/or revenue.
Most customers that matter to a business don't churn due to subpar user experience - discounting, roadmap, and dedicating a subset of engineering staff to handle bugs originating from a handful of the most important accounts is enough to prevent churn.
That said, this advice only really holds in the US (and that too in the major tech hubs). If you work in Western Europe you're shit out of luck as a SWE - management culture there just doesn't give a shit about software, because for most Western European businesses software is a cost center, not a revenue generator.
>> Attacks like this are not helped by the increasingly-common "curl | bash" installation instructions ...
> It's not really any different than downloading a binary from a website, which we've been doing for 30 years.
The two are very different, even though some ecosystems (such as PHP) have used the "curl | bash" idiom for about the same amount of time. Specifically, binary downloads from reputable sites have separately published hashes (MD5, SHA, etc.) to confirm what is being retrieved along with other mechanisms to certify the source of the binaries.
Which is the reason why it's better to actually cryptographically sign the packages, and put a key in some trusted keystore, where it can actually be verified to belong to the real distributor, as well as proving that the key hasn't been changed in X amount of days/months/years.
Still doesn't address the fact that keys can be stolen, people can be tricked, and the gigantic all-consuming issue of people just being too lazy to go through with verifying anything in the first place. (Which is sadly not really a thing you can blame people for, it takes up time for no easily directly discernable reason other than the vague feeling of security, and I myself have done it many more times than I would like to admit...)
> If the attacker already controls the download link and has a valid https certificate, can't they just modify the published hash as well?
This implies an attacker controlling the server having the certificate's private key or the certificate's private key otherwise being exfiltrated (likely in conjunction with a DNS poisoning attack). There is no way for a network client to defend against this type of TLS[0] compromise.
Thank you for sharing a non-trivial working example of a sandbox-exec configuration. Having an exemplar such as what you have kindly shared is hugely beneficial for those of us looking to see what can be done with a tool such as this.
> A lot of how I form my thoughts is driven by writing code, and seeing it on screen, running into its limitations.
Two principles I have held for many years which I believe are relevant both to your sentiment and this thread are reproduced below. Hopefully they help.
First:
When making software, remember that it is a snapshot of
your understanding of the problem. It states to all,
including your future-self, your approach, clarity, and
appropriateness of the solution for the problem at hand.
Choose your statements wisely.
And:
Code answers what it does, how it does it, when it is used,
and who uses it. What it cannot answer is why it exists.
Comments accomplish this. If a developer cannot be bothered
with answering why the code exists, why bother to work with
them?
To your first point - so are my many markdown files that I tell Codex/Claude to keep updated while I’m doing my work including telling them to keep them updated with why I told them to do certain things. They have detailed documentation of my initial design goals and decisions that I wrote myself.
Actually those same markdown files answer the second question.
> If a developer cannot be bothered with answering why the code exists, why bother to work with them?
Most people can't answer why they themselves exist, or justify why they are taking up resources rather than eating a bullet and relinquishing their body-matter.
According to the philosophy herein, they are therefore worthless and not worth interacting with, right?
>> Works if you supply the correct include path(s)
The location of Standard C headers do not need to be supplied to a conformant compiler.
>> You could arguably fault ccc's driver for not specifying the include path to find the native C library on this system.
This is not a good implementation decision for a compiler which is not the C compiler distributed with the OS. Even though Standard C headers have well-defined names and public contracts, how they are defined is very much compiler specific.
Well this compiler was written to build Linux as a proof of concept. You don't need a libc for building the kernel. Was it claimed anywhere that it is a fully compliant C compiler?
That's kind of moving the goal post no? They set out to build a C compiler that could compile the kernel, it can do that just fine?
Searching for "compliant" in the README doesn't seem to indicate that building a "conformant compiler" was even the goal here, so not sure why that's suddenly should be a requirement.
This.
:-p
reply