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 -
There is no meaninfful distinction between programmers and software engineers. I consider myself a programmer because I feel like it captures what I do more accurately, and refer to myself as a software engineer in situations where it is financially beneficial. Software engineering is programming plus bureaucracy. Lots of things involve bureaucracy. When it comes to software engineering, programming is the main bit. If you take out the programming, it's not software engineering anymore. I have no patience for someone who thinks they are contributing technically by building a pie-in-the-sky UML diagram and demanding that actual programmers implement their out of touch vision.
I think you're right about that this is where we disagree. If we take doing science as "making progress on our ability to predict and manipulate the physical world", well that applies to the electron microscope salesmen, academic departmental secretaries, directors of corporate research orgs, plumbers who install chilled water systems in labs, the maintainers of python and r, and any number of other people who contribute in some small way to the broad economic activity of advancing science. You my protest that since science coordinators work a bit closer to the main body of the academic work than the directors of a corporate lab, they are scientists, but both of those roles are mostly about coordinating the technical work.
Within our current system, that's what you need to do to push research forward. It doesn't mean you would be a scientist in that situation.
I'm not blaming PIs for the current state of affairs. They are operating within a system of constraints and incentives that they had no role in building. I'm just pointing out that they are not scientists, despite being the best trained people to fulfill such a role.
Excellent point! My follow-up question is therefore: what actual utility is there in distinguishing some of the jobs (professions? tasks?) that progress our ability to predict and manipulate the physical world as "scientist"?
I do think that this utility exists and is important. It reminds me of Feynman's description of cargo cult science:
In an organization whose purpose is to progress in our ability to predict and manipulate the physical world--and which has a solid track record of effectively making this progress--who are the people that are essential to the enterprise, and who are in necessary supporting roles?
If the latter: do they require transferable set of skills that are not particular to this specific enterprise? The plumber who installs the chilled water system is such; so is the CPA in HR; so is the janitor. The lab manager (like, in a chem lab) would need to have specialized knowledge to do her job, but it's still transferable set of skills (solid Bachelor's level knowledge of chemistry plus great organizational skills). These people do useful work that enable the enterprise, but they are not essential.
It's useful to reserve the term "scientist" for the former--those who are essential to the enterprise--to keep the telos of their profession foremost in mind. It's useful, because the scientist's telos is frequently in direct contradiction with goals people have (e.g., getting that publication after you put in so much effort into that experiment, if only those couple of observation points weren't undermining your hypothesis). Let me quote Feynman once more:
Yeah, I think I basically agree with that unless I'm misreading you. I think "scientist" has a bunch of cachet, and we should assign that cachet to the people doing what is normally thought of as science rather than pushing paper.
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link