site banner
naraburns  nihil supernum  1yr ago (text post)   35414 thread views

Culture War Roundup for the week of October 3, 2022

This weekly roundup thread is intended for all culture war posts. 'Culture war' is vaguely defined, but it basically means controversial issues that fall along set tribal lines. Arguments over culture war issues generate a lot of heat and little light, and few deeply entrenched people ever change their minds. This thread is for voicing opinions and analyzing the state of the discussion while trying to optimize for light over heat.

Optimistically, we think that engaging with people you disagree with is worth your time, and so is being nice! Pessimistically, there are many dynamics that can lead discussions on Culture War topics to become unproductive. There's a human tendency to divide along tribal lines, praising your ingroup and vilifying your outgroup - and if you think you find it easy to criticize your ingroup, then it may be that your outgroup is not who you think it is. Extremists with opposing positions can feed off each other, highlighting each other's worst points to justify their own angry rhetoric, which becomes in turn a new example of bad behavior for the other side to highlight.

We would like to avoid these negative dynamics. Accordingly, we ask that you do not use this thread for waging the Culture War. Examples of waging the Culture War:

  • Shaming.

  • Attempting to 'build consensus' or enforce ideological conformity.

  • Making sweeping generalizations to vilify a group you dislike.

  • Recruiting for a cause.

  • Posting links that could be summarized as 'Boo outgroup!' Basically, if your content is 'Can you believe what Those People did this week?' then you should either refrain from posting, or do some very patient work to contextualize and/or steel-man the relevant viewpoint.

In general, you should argue to understand, not to win. This thread is not territory to be claimed by one group or another; indeed, the aim is to have many different viewpoints represented here. Thus, we also ask that you follow some guidelines:

  • Speak plainly. Avoid sarcasm and mockery. When disagreeing with someone, state your objections explicitly.

  • Be as precise and charitable as you can. Don't paraphrase unflatteringly.

  • Don't imply that someone said something they did not say, even if you think it follows from what they said.

  • Write like everyone is reading and you want them to be included in the discussion.

On an ad hoc basis, the mods will try to compile a list of the best posts/comments from the previous week, posted in Quality Contribution threads and archived at /r/TheThread. You may nominate a comment for this list by clicking on 'report' at the bottom of the post and typing 'Actually a quality contribution' as the report reason.

24
Top Bottom New Old Comments
Jump in the discussion.

No email address required.

The latter is a more 'rigorous' approach where students are taught the fundamentals such as data types, structures, flow, interpreter vs compiler, etc first; Then they are made to write programs. These programs are sometimes gamified but not to the extent as the former[...] I consider the latter "imparting knowledge" method superior. It's more in line with all the hard sciences I have been taught and all the good programmers I am aware of claim to have been taught using this method.

I realized as an adult that I do not retain knowledge if I am given that knowledge before I have any way to apply it. I suspect I'm not alone in this; but regardless, I strongly prefer the teaching methodology where you are made acquainted with tools by being given problems which necessitate using those tools. By "tools", here, I refer to algorithms and data structures, among other things. (I think this is why, even though I loved my Algorithms and Data Structures courses, I hated Operating Systems and whatever one it was that taught us assembly language. I retained very little of those and do not count them among the good or useful courses I took.)

I'm aware that this "knowledge-first-to-use-it-later" approach is similar to how the hard sciences are taught; I hated it there as well.

My actual start in programming came from hacking around in the Civilization 4 Python codebase, where I built mods for Fall From Heaven 2 and by necessity had to learn programming syntax-- I was only formally educated in programming later. Contrary to what your argument above would predict I was by far the strongest coder in my graduating class, and went on to get a job in FAANG (where I was, in my judgement, roughly at the top 20% of programmer strength in the company.)

So I don't know the total of what my "ideal programmer education" consists of, but I'm pretty sure a big chunk of it would involve writing a self-designed mod for the game Slay The Spire.

Okay okay, hear me out, this has a number of advantages:

  1. Slay the Spire is entirely programming-first. There is no "editor" interface, as a Unity game would have.

  2. Slay the Spire modding has, as its first step, decompiling the codebase. This gets your student exposure to "the act of having to understand somebody else's extremely nontrivial code".

  3. The codebase is also written using fairly reasonable best practices, particularly for a gaming studio-- it uses polymorphism to deal with all the myriad cards and their effects, which allows you to see very intuitively how polymorphism is used in the wild and why it's valuable. (I know that in my own programming education all of our programs were trivial enough that interfaces and abstract classes seemed weird and pointless, and none of my instructors could give what felt like adequate explanations for their use.)

  4. You can get something pretty cool out the other side-- a game mod! Having something cool and nontrivial that you're in the process of building is worth any number of credit points in inspiring motivation to actually learn programming.

  5. It's Java, which is a very standard programming language which features automated memory management.

So I think if I were designing a programming practicum it would feature game-modding as a big part of it, with perhaps some Code Combat or similar coding game in the first couple of weeks to familiarize students with the basic syntax and philosophy around programming in some reasonably entertaining format. And, of course, some problem sets later that showcase situations where students are given no choice but to use the standard data structures and algorithms.

What were you doing with FFH? I might have some of your work installed.

I'm a very poor programmer, the only thing I did was edit some Leader files to stack good traits on an Amurite leader in Ashes of Erebus so I could try to make an archmage Master of all the elements and achieve omnipotence.

I did the More Leaders Modmod!

The coding was extremely low-quality and the Python was probably buggy as hell. But it was mine.

EDIT: Wait, I think Ashes of Erebus did end up incorporating some of my work! How's that project going, by the by?

I think Ashes is basically finished. They added a race of Hamstalfar, hamsters lording over elves. That broke my immersion somewhat.

Was your More Leaders anything to do with the Minor/Emerging leaders in Ashes of Erebus?

I added a bunch of minor leaders, but I didn't do any of the mechanics behind Minor Leaders in general.

I... did not much like the Hamstalfar.

I also have the experience that I am incapable of remembering things that are not applicable.

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


Recommended Posts And Communities

Recommended Realtime Chats