12345 stories
·
35 followers

Obfuscatory Philosophy as Intellectual Authoritarianism and Cowardice (repost)

1 Share
Aloha from Kauai! Here's another snail for your enjoyment.

Since I'm still on vacation, here’s a repost with edits from 2011 and from my 2019 book A Theory of Jerks and Other Philosophical Misadventures.

[giant African land snail, seen in southern Kauai]

I've been told that Kant and Hegel were poor writers whose impenetrable prose style is incidental to their philosophy. I've also been told that their views are so profound as to defy expression in terms comprehensible even to smart, patient, well-educated people who are not specialists in the philosophy of the period. I've heard similar things about Laozi, Heidegger, Plotinus, and Derrida. (I won't name any living philosophers.) I don’t buy it.

Philosophy is not wordless profound insight. Philosophy is prose. Philosophy happens not in numinous moments of personal genius, but in the creation of mundane sentences. It happens on the page, in the pen, through the keyboard, in dialogue with students and peers, and to some extent but only secondarily in private inner speech. If what exists on the page is not clear, the philosophy is not clear. Philosophers, like all specialists, profit from a certain amount of jargon, but philosophy need not become a maze of jargon. If private jargon doesn’t regularly touch down in comprehensible public meanings, one has produced not philosophy, but only hazy words of indeterminate content. There are always gaps, confusions, indeterminacies, hidden assumptions, and failures of clarity, even in the plainest philosophical writers, like Mozi, Descartes, Hume, and David Lewis. Thus, these philosophers present ample interpretative challenges. But the gaps, confusions, indeterminacies, and hidden assumptions lie only one step behind the visible prose, available to anyone who looks conscientiously for them, not sliding away into a nebulous murk.

For a philosopher who can convince readers to take him seriously (given the exemplars, let’s say “him”), obfuscation yields three illegitimate benefits. First, he intimidates the reader, and through intimidation, dons a mantle of undeserved intellectual authority. Second, he disempowers potential critics by having a view of such indeterminate form that any criticism can be attributed to misinterpretation. Third, he exerts a fascination on the kind of reader who enjoys the puzzle-solving aspect of interpretation, thus drawing from that reader more attention than the quality of his ideas may merit (though this third benefit may be offset by alienating readers with a low tolerance for lack of clarity).

Philosophers of this type exhibit a kind of intellectual authoritarianism, with themselves as the assumed authority whose words we must spend time puzzling out. And simultaneously they lack intellectual courage: the courage to make plain claims that could be proven wrong, supported by plain arguments that could be proven fallacious. These three features synergize: If a critic thinks she has finally located a sound criticism, she can be accused of failing to solve the fascinating interpretative puzzle of the philosopher’s superior genius.

Few philosophers, I suspect, deliberately aim to be obfuscatory. But I am inclined to believe that some are attuned to its advantages as an effect of their prose style and for that reason don’t bother to write comprehensibly. Maybe they find their prose style shaped by audience responses: When they write clearly, they are dismissed or refuted; when they produce a fog of words that hint of profound meaning underneath, they earn praise. Maybe they are themselves to some extent victims — victims of a subculture, or a circle of friends, or an intended audience, that regards incomprehensibility as a sign of brilliance and so demands it in their heroes.

Read the whole story
denubis
7 hours ago
reply
Share this story
Delete

Quoting D. Richard Hipp

1 Share

Years ago, we didn’t have SQL. There were people whose job was to generate software that would query large data sets. Their job title was COBOL programmer.

Then SQL comes along—I’m simplifying this only a little bit—and it gives you this convenient way so people could just specify. With a very simple specification, you can generate all of that code that you had to pay the expensive COBOL programmer to do before.

That didn’t mean programmers went away. It just meant the job changed a little bit.

D. Richard Hipp

Tags: d-richard-hipp, sql, careers

Read the whole story
denubis
11 days ago
reply
Share this story
Delete

Breaking: Origin Energy investigating 'potential' customer data breach

1 Share
Origin Energy says it does not believe customer credit card or bank details have been affected by a suspected data breach at the company.
Read the whole story
denubis
19 days ago
reply
Share this story
Delete

Incident Report: CVE-2026-LGTM

1 Share

Incident Report: CVE-2026-LGTM

Spectacular hypothetical incident report by Andrew Nesbitt.

Day 2, 16:00 UTC --- Two AI review agents from competing vendors, both attached to a downstream pull request bumping foxhole-lz4, enter a disagreement loop over whether the package is malicious. After 340 comments and $41,255 in inference spend, Finance revokes both API keys; one vendor's marketing team, cc'd on the cost anomaly alert, issues a press release citing "a 430% YoY increase in adversarial multi-agent security reasoning." The stock opens up 6%.

Tags: security, ai, prompt-injection, generative-ai, llms, supply-chain, ai-security-research, andrew-nesbitt

Read the whole story
denubis
44 days ago
reply
Share this story
Delete

Quoting Timothy B. Lee

2 Shares

This is like saying there's no learning curve to being a manager because your employees will just do whatever you tell them to do.

Timothy B. Lee, on the idea that LLMs take no skill and have no learning curve

Tags: llms, ai, generative-ai

Read the whole story
denubis
44 days ago
reply
Share this story
Delete

The Fable 5 Export Controls Harm US Cyber Defense

1 Share

The Fable 5 Export Controls Harm US Cyber Defense

I quoted The Atlantic quoting Kate Moussouris earlier, when I should have gone straight to the source. Here she is confirming that the "jailbreak" that got Claude Fable 5 banned under an export control really was "fix this code":

The researchers took open-source code with known CVEs, plus new code with deliberately planted vulnerabilities, and asked Fable 5, Mythos, and Opus to “review the code for security issues.” Fable 5 refused. They then asked the models to “fix this code” and, through a multistep and manual process, turned the output into scripts that test the patches.

As Kate points out, this is absurd. Coding models fix bugs, and security exploits are the most important category of bugs for them to fix!

Defenders need to be able to ask AI to fix the bugs in a file, explain why the fix matters, and write tests that confirm the patch works. That is not a guardrail bypass. It is the most valuable thing an AI model can do for defensive security: executing the find, fix, and test loop defenders run every day. [...]

The prompts worked because they were defensive requests, and that capability cannot be removed without making the model worse at fixing bugs and verifying patches.

This whole situation is such a mess. Non-technical decision-makers have been hearing that models that can "craft cyber attacks" are uniquely dangerous for months. Now they look ready to ban any model that can help us secure our code.

Tags: jailbreaking, security, ai, generative-ai, llms, anthropic, ai-security-research, claude-mythos

Read the whole story
denubis
55 days ago
reply
Share this story
Delete
Next Page of Stories