It's been a long time since I said it, and who knows if there'll be a chance to do so in the future. So here goes:
I've learned more by being on Twitter than I could have imagined, and it was possible only because so many excellent people say so many amazing things. So thank you

The people can always be brought to the bidding...tell them they are being attacked, and denounce the naysayers for lack of patriotism and exposing the country to danger.

Hermann Goring

We've seen reports of Yoruba leaders asking President Buhari to stop the war and sack service chiefs immediately as a way of beginning restructuring.Our country is sitting on a keg of gunpowder they claim. Once again partisan hacks want to snatch victory from the jaws of defeat.

You see, when you are fighting small limited wars there is a natural inclination , on the part of politicians not directly impacted by the war to want to blow things out of proportion. There is a basic disconnection now in this country between the population and the war

....and i find it quite frankly. Frightening. Compared to what was obtainable 2015, the security situation in Nigeria has vastly improved yet the media ..and partisan hacks portray a much more pessimistic narrative.

Consider that in 2015 over 21 Local government areas and 2.6 million Nigerians were cut off from the rest of the country, under the administration of a caliphate in Nigeria for 16 months. A huge chunk of the northeast was no mans country.

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.

I am done giving this doctor or team grace. I started with "We are tremendously grateful for all you are doing." He seemed irritated to speak to us. Literally I asked, "What is the likelihood our mom will die on current support, in the next 24 hours, so we can plan travel?"

He hammered us with how severe this was and that was. Yes, that is why I am asking the question. "We are asking you to be a thought partner so we can make responsible decisions as the family." I had had pre-conversations with doctor friends to understand the numbers and prognosis

He said "It would be illegal for me to tell you that she won't die, then she dies." Yes, that is why I said LIKELIHOOD - critical care docs deal in likelihoods. It so frustrating to be on this side and not get a fraction of the standard that I have been held to and hold myself to

Then I made the error of saying, "I'm a pediatrician, I literally do this work on family-centered, compassionate care." to which the charge nurse answered, "It is not the work we do. We keep people alive." End of life care IS your job. Planning IS your job. It's not just numbers

Compassion is not only a pediatric thing while critical care/end of life can proudly lack it. I've had more end of life conversations than I want to remember. My mom is not numbers. She is a human being. I am modulating my voice, complimenting you, leveraging my network.