Be advised: this thread is not for serious in-depth discussion of weighty topics (we have a link for that), this thread is not for anything Culture War related. This thread is for Fun. You got jokes? Share 'em. You got silly questions? Ask 'em.
- 124
- 1
What is this place?
This website is a place for people who want to move past shady thinking and test their ideas in a
court of people who don't all share the same biases. Our goal is to
optimize for light, not heat; this is a group effort, and all commentators are asked to do their part.
The weekly Culture War threads host the most
controversial topics and are the most visible aspect of The Motte. However, many other topics are
appropriate here. We encourage people to post anything related to science, politics, or philosophy;
if in doubt, post!
Check out The Vault for an archive of old quality posts.
You are encouraged to crosspost these elsewhere.
Why are you called The Motte?
A motte is a stone keep on a raised earthwork common in early medieval fortifications. More pertinently,
it's an element in a rhetorical move called a "Motte-and-Bailey",
originally identified by
philosopher Nicholas Shackel. It describes the tendency in discourse for people to move from a controversial
but high value claim to a defensible but less exciting one upon any resistance to the former. He likens
this to the medieval fortification, where a desirable land (the bailey) is abandoned when in danger for
the more easily defended motte. In Shackel's words, "The Motte represents the defensible but undesired
propositions to which one retreats when hard pressed."
On The Motte, always attempt to remain inside your defensible territory, even if you are not being pressed.
New post guidelines
If you're posting something that isn't related to the culture war, we encourage you to post a thread for it.
A submission statement is highly appreciated, but isn't necessary for text posts or links to largely-text posts
such as blogs or news articles; if we're unsure of the value of your post, we might remove it until you add a
submission statement. A submission statement is required for non-text sources (videos, podcasts, images).
Culture war posts go in the culture war thread; all links must either include a submission statement or
significant commentary. Bare links without those will be removed.
If in doubt, please post it!
Rules
- Courtesy
- Content
- Engagement
- When disagreeing with someone, state your objections explicitly.
- Proactively provide evidence in proportion to how partisan and inflammatory your claim might be.
- Accept temporary bans as a time-out, and don't attempt to rejoin the conversation until it's lifted.
- Don't attempt to build consensus or enforce ideological conformity.
- Write like everyone is reading and you want them to be included in the discussion.
- The Wildcard Rule
- The Metarule

Jump in the discussion.
No email address required.
Notes -
Your results are worse than mine, but I'm in a similar boat. The results that the boosters are seeing are not what I am seeing in my professional life.
I can approximate what the boosters are seeing in personal projects, if I keep the scope small, and I use python, and the project doesn't involve much state management, and I write a spec that is roughly the same size as the codebase that would exist if I were to write it by hand.
This kind of tracks with the handful of AI enthusiasts I know in real life, too. The first category is professional programmers. When I ask what problems they solve with it, they tell me they're using AI to write an AI agent orchestration framework to better run their AI. When I ask what they'll use that tool to do, I'm told to shut up, because AI is the future and you can't be left behind. The second category is non programmers who ask Claude to process a CSV file, and this blows their dick clean off. The idea that you can process a CSV file and you don't even need Excel to do it is a mind-altering experience for them. The fact that Claude is doing a tool call that runs ten lines of python is irrelevant. This is the future. They'll keep rebuilding that same deterministic python script from an elaborate prompt every single month, because holy mother of cyber-jesus, this saves them half an hour in Excel every month.
Everyone else I know is either possessed of a terrifying antipathy, or can't muster up anything more enthusiastic than "it's ok, I guess".
On an unrelated note - do you know why .net projects like to keep their unit tests in a segregated project? Most other languages that I've used have a convention where the unit tests are in a separate folder in the same project.
I donno, why do most other languages comingle their production code with their unit tests? I can't speak for any official reason, but I know managing large dotnet solutions, testing projects need to be flagged with true in it's project file or some shit like that. Otherwise test runners don't find it. They usually also have a bunch of nuget packages pulled in, like xunit or MSTest that your production project won't need. They'll probably have some resources embedded in them to facilitate testing which you almost certainly do not want shipped in production.
Man, I was checking the dependencies xunit3's nuget pulls in now. Shit looks like a maven package.
More options
Context Copy link
More options
Context Copy link