A Cradlesong

By which the Tepanecs in former times praised Ahuizotl, Mexica king. A composition of Nohnohuiantzin of Nextenco, singer and nobleman.

I. Child, Boy, Man

A

Ah, my song begins within the flower house,
And I carry my little one safe in my arms.

1/

1⃣
At the moment #POTUS is sitting on a stack of #Trump cards, he's just waiting to unleash a royal flush!
He has court cases that will go to #SCOTUS and thanks to the Texas case, he's now aware how to file them properly under article 3 not 2, so SCOTUS will be forced to listen.

2⃣
#Trump now has the #DNI report. #Barr stepped down and can now be a witness, he did his job. #Durham is special counsel and can prosecute, in any state.
He’s letting civil, criminal and federal courts fail to handle the situation properly so he can use military tribunals.

3⃣
#Trump has ALL the data from the #NSA, the #Kraken supercomputer, the #Alice #supercomputer, and likely many more computers, unknown to us.
He has the dueling electors from 7 state legislatures. He has VP #Pence, as the final arbiter of which ballots to accept.

4⃣
#Trump has the #InsurrectionAct, the #NDAA, the national emergency, the 14th amendment, the 2018 executive order, the 2017 very first EO, the #Patriot Act, the #FISA warrants, the Declassification of everything, people swearing affidavits by the 1000s.

5⃣
#Trump has all the statistical data being analyzed along with the videos, emails, phone calls and bank transfer statements showing the coordination of the #coup d'etat.
He has #RICO and he has the #CrimesAgainstHumanity videos. #Wikileaks just dropped extensive information

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.

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/

VALENTINE DAY CELEBRATION: FRSC CAUTIONS MOTORISTS AGAINST EXCESSIVE SPEED, DRUNK DRIVING AND RECKLESSNESS ON THE ROAD.

Owing to the need to ensure a safe and crash free celebration during the 2021 Valentine Day celebration, the Federal Road Safety Corps has warned the teaming community of celebrants and other road users, to desist from indulging in drunk driving, avoid excessive speed,

and resist the temptation to drive recklessly so as to mitigate all incidences of road traffic crashes during the celebration.

The Corps Public Education Officer, @BisiKazeem who made this public, said that the Corps Marshal, Dr Boboye Oyeyemi has directed Commanding Officers across board to double their efforts by ensuring massive deployment of Officers and Men for enhanced visibility,

adequate traffic control, and maximum enforcement of all COVID-19 protocols amongst motorists.