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.
Jump in the discussion.
No email address required.
Notes -
All I am hearing is "just read the traffic code and you'll be fine, man. No policeman is ever going to ticket you for something which is not in the traffic code."
Sure, the policeman will find a section in the traffic code to ticket you, and that will not be difficult because some of the sections are very broad. For example, "reckless endangerment" could cover anything from your pet jumping out of your convertible mid-drive to you getting stuck on the highway with an empty tank. Likely, the traffic code will not explain how your car needs fuel and how to check the fuel gauge. Knowing that you are forbidden from recklessly endangering others does not mean that you know how to do that.
If someone wants to learn C++, about the worst advice in the world would be to tell them "just read through ISO/IEC 14882:2024, everything you need to know about C++ is in there". Sure, it would be technically correct that if they stick to the standard, use a standard-compliant compiler correctly (a subject very much not covered by the standard) then their program will have a well-defined runtime behavior, but even if that person is a genius able to wade through ENBF syntax rising to their chin and coming out with a solid understanding of how actual code would look like on the other side, they would spend most of their remaining lifespan independently re-discovering the principles of good software engineering.
For electrical installations of low-voltage systems, the relevant local standard likely refers to IEC_60364. Your would-be electrician will likely want the sections (1), (4), (5) and (6), each of which costs about 280 swiss franks in the IEC web store. Part 1, Fundamental principles, assessment of general characteristics, definitions is all of 49 pages, so I would not expect full electrical engineering 101 course full of comic strips to teach how to apply wire ferrules or use luster terminals or warn you that single strand wires will eventually break if bent in opposite directions repeatedly (or whatever, I am very obviously not an electrical engineer). Likely, the standard will start by saying that electrical installations should only be performed by licensed professionals (which is part protectionism and part that you can not reasonably trust a layman to understand the standard from reading it), and your self-taught handyman will be breaking at least that part of the standard.
More options
Context Copy link