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.
- 53
- 7
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 -
Obviously, some subset of 'make anything that existing computers do' for one. Develop a game, create a nice UI for something, simulate (at any level of detail - from 'very simple model' to 'the quantum-mechanical interactions of some chemical') some physical process, cause some physical process in a manufacturing process or robot, compute some property of a mathematical system (wondering of some weird arithmetic statement is true? Check it for the first 10^15 positive integers - at 1B/second, that'll only take a week or two!). There's also lots of complex problems required to implement programming - 'datastructures and algorithms' is quite math-ish and complicated, but every technical field has depth to it - implementing distributed systems is hard, writing very fast specialized algorithms that depend on the details of hardware features is complex, designing programming languages and compilers is hard, graphics is hard, 3D rendering is hard, ML is hard, all of these have a ton of intellectually complex depth to them.
That's weighted for 'interestingness', of course, 'make a boring web app' has a lot more job openings than 'distributed systems'
Not everyone can do most of these, ofc. But people specialize, although not necessarily for a whole career! A good programmer should be able to learn the very basic basics of any subarea of one of those within a few weeks, and dive deep into some technical part of any of that and do something interesting and tough in a few months - a year. If any of that sounds interesting, (once you can, like, write a program that 'takes a list and sorts' it), just try it! Write a game, even if it starts as simple as 'square moves around a 2d area and shoots circles at other squares' - make simulator + 3D renderer of some physics thing, even if the first version is "compute the trapezoid method approximation of an integral and graph it" - figure out what 'type theory' is, scrape all the text on 'themotte' and make a https://hn.algolia.com tier search for it, up to you.
Project Euler is basically abstract math problems that also require programming to solve, that might be fun once you know a bit.
More options
Context Copy link