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.
- 134
- 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 -
So, I had an interesting problem at work, that revealed something fascinating I think.
I have to beat around the bush some, so bear with me. We're using a popular framework for our database layer. We went to do things to this database that theoretically the database is capable of, but the framework doesn't support. Sad face. All the web searches, and associated AI formulated answers confirm, it's not possible do said thing in said framework.
Except it is. The Framework is open source. You can just read the source code. Turns out you can ask for the handle to the underlying interop pointer, and it'll just give it to you. You don't even have to do weird fucky things like dig around in private data space. It's a public API call to just get the interop pointer. The driver it's calling is open source too, and you can just call the function you want on the interop pointer it gives you, and it just works. It's fine. If it's confusing, the test cases for the driver in it's github even shows you exactly how to do it, multiple ways. Reading unit tests are awesome for stuff like that. This is the furthest thing from impossible. It's practically spelled out for you with examples if you just read the fucking code.
So, why does AI all think it's impossible? Because as of 3 years ago, this functionality wasn't exposed by the driver. So all the stack exchange questions about this correctly stated that as of 3+ years ago, this was impossible. LLMs got trained on stack exchange (supposedly), and now stack exchange is a dead site. The LLMs (supposedly) killed off the source of knowledge they were being trained on, and now they can't learn that a few years later this task is not just possible, but trivially easy in like, 6 lines of code. Totally within the remit of the typical "how do I do thing" programming question.
Just point it at the source code or github? Sometimes I get issues where it doesn't know what the right conventions are for calling its own API or recently released APIs, since that obviously comes after its training and I say 'go check it up' and then it does that.
Ideally it should do this by default, true.
But why? Within 30 minutes of finding the code, I found my answer. Within 10 minutes of dicking around in a sample project, I had my proof of concept. How would an LLM have improved on that? I don't need the LLMs validation or approval.
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link