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.
- 86
- 2
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 -
Best I can do is complain about how wonky the budget is for a somewhat important piece of shipping software. You'd think we could get $ENTERPRISE licenses squared away easily, we're not some fly-by-night shop. Because we don't have $ENTERPRISE licenses we apparently aren't allowed to install $TOOLS I need to unify our Unix and MS build processes, and we can't just stand up a build server running, say, $DROP_IN_ENTERPRISE_ALTERNATIVE or something on it because policy. Devsecops is goofy.
Also, as a sidebar - apparently barely anybody has put in the effort to try to build $WELL_KNOWN_INFRA_TOOL for Windows on Unix in the last decade and a half, and somewhere down the stack it just completely blows up because of preprocessor hell in a cross-build environment. My favorite thing in the world is when a header is included with nice and neat capitalization that doesn't match the actual file's (entirely lowercase) capitalization, so it builds just fine on MS because MS filesystems aren't case-sensitive and dies on Unix because someone wanted their includes to look pretty. I have done black magic to this dependency tree to get it close to building and then it still dies because of platform-specific linker options that are getting improperly set in a CMakeList. There's reasons why we're building this from source instead of using a package for it, but it's a huge morass of fiddly that I'm allowed to keep bashing my head on because if we get this to work, the payoff for our whole CI environment is huge. Somehow I've only had two drinks in the last six months.
(Apologies if you find the formatting obnoxious but I'm trying to keep a minimal degree of opsec.)
MinGW and MSVC capitalize their header names differently, so it's possible they were correct for the person who wrote them.
More options
Context Copy link
My civil-engineering organization only recently upgraded from a version of CAD software that was literally twenty years old—not for budgetary reasons, but because the old codger in charge of the CAD unit saw no need to upgrade, and dug in his heels to resist upgrading until just a few years before he retired. There were regular problems with renewing the license for it.
Ooooof, that sounds rough. At least my shop is aware of the licensing problem - part of our major infra push is an effort to fix it, but we're still kinda kneecapped by policy at the end of the day.
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link