Strangely enough, I can kinda relate to him on a certain level. He's a wise cracking tough guy, but once you dig deep enough you start to realize he has a big heart. He makes the wrong decisions sometimes but it's hard to blame him considering what he's been through.

So, here's my contrarian take on Why Trunk-Based Development Is Great But Probably Won't Work For You. Buckle up, it's a long one.

From time to time I talk about, or boost someone else's discussion of, "classical" continuous integration/trunk-based development/push-to-master/whatever. I do this because I've personally worked like this and I genuinely think it's a marvelous way to write software.

I've also, at this point in my career, failed—a bunch of times!—to bring this technique into practical use on the teams and organizations I've worked with. As a result, while I still do it myself, I don't focus as much on encouraging it in others.

The technoculture that's presently in vogue is what I think of as async/individual—optimize for the individual, performance-manage the individual, decouple the individual from others so they can be their best, most productive, most heroic selves.

This is in contrast to what I think of as sync/team—a culture that leans into interdependence and collaboration. If you've never worked on a team that collaborates very closely every day for months or years on end (and likes it) you've likely not experienced a team like this.

Nonlawyer Explainer Thread: On Keeping One's Mouth Shut

It occurs to me that certain private-jet-flying seditionists who continue to yammer on Twitter about their DC excursions provide us with the opportunity to do a little hypo to explore the benefits of silence.

So let's explore what a hypothetical law enforcement interview *might* look like in this situation. I'm not - I want to make clear - drawing from experience as a lawyer here.

I AM NOT A CRIMINAL LAW ATTORNEY.

Instead, I'm mostly drawing from discussions with my father-in-law.

My father in law is a now-retired homicide cop, and we've had a lot of discussions (especially since I started law school) about criminals and interviews over the years.

So with that in mind, let's look at this hypo.

ALSO - Simplifying for Twitter character counts.

*Knock*
*Door opens*
Agent: Ms [Name]? I'm Agent Smith, and this is Agent Jones. We're with Agency. We'd like to talk to you if you've got a minute.

Ms X: Oh? Is this about that thing at the Capitol?

[Yes, it seems insane but if you're worried about something specific and the cops show up, blurting out something like that is totally a thing that can happen.]

@jeffreyatucker In the end, it is all a natural consequence of a very human foible, namely that we all do everything we can to blame anybody or anything else for our problems, if we can get away with it. It's the reason why rulers start wars to squelch domestic dissent - macro and micro the same

The very notion of the germ theory of disease revolves around this and while it is good for selling medical interventions, treatments and pharmaceuticals, it is no good for either personal health, or public health in any way. We need to start looking at health on a holistic level

More of a systems approach to health would get us to see that the whole instinct to stamp out viruses, like the very counter-factual notion of "zero Covid," and other nonsense, are driven by this need to blame somebody or something else for our problems, so we can have our cake

and eat it too, i.e. we can pass the blame to others and go and kill them, be they bugs or other people (lockdowns???). The results are disastrous for health on both a personal and a public level, and we continue on a path of assured self-destruction. But times are changing, now.

Lifestyle Medicine @aclifemed provides the new paradigm, more of a systems approach to health, in which personal responsibility for our habits comes first, starting with nutrition. Immune systems become depressed by fatigue, stress, inner conflict, malnutrition and so on. Change

There is a highly instructive symposium on "Veil of Ignorance" #ProcessTracing in the new @APSAtweets QMMR publication https://t.co/nxqEQ9HaRz There is lots to say ab it. For now, I want to focus on whether (causal) qualitative research has a problem w/ confirmation bias that 1/

needs to be addressed.
In short, Veil of Ignorance process tracing aims to blindfold the data collectors and analysts to the hypotheses to reduce risk of confirmation bias.
Proposal receives a lot of criticism by all respondents, partly for valid reasons, partly not, IMO 2/

If there was no bigger issue with confirmation bias, there would not be much benefit in talking about blinding in qualitative research.
As Beach notes, the intro to the symposium does not present evidence that bias is a problem. This is correct, but there is also no evidence 3/

that confirmation bias is not a problem. It's an absence of evidence situation with regard to comprehensive, direct evidence, i.e. from verification studies of qualitative research (for studies that are built on an epistemology for which the idea of verification makes sense). 4/

However, I'd say there is circumstantial evidence that confirmation bias is a problem.
1) Evidence for confirmation bias in quantitative research: The developments around #OpenScience and transparency in quantitative research in different disciplines present diverse evidence 5/