And by & large, I’ve taken to call it “DevOps”, because the DevOps community have taken up much of the mantle @KentBeck & the XP community started with. & Kent has independently focused on safe small changes deployed to production. Which is DevOps.
1/
Thinking about this tweetstorm, one of the issues I’ve run into as an engineering leader is what to call the software engineering stuff that’s “agile” given that the Agile Community(tm) has killed the brand.
I might do an \u201cagile\u201d tweet storm to the effect that all the attention is to the least leveraged portions of the value stream. Interest?
— Arien Malec (@amalec) October 26, 2019
And by & large, I’ve taken to call it “DevOps”, because the DevOps community have taken up much of the mantle @KentBeck & the XP community started with. & Kent has independently focused on safe small changes deployed to production. Which is DevOps.
Much of the art here is making changes safe enough to deploy to production continuously. And to do that, we need to design incrementally, test obsessively, take architecture seriously so we decompose dependencies. & we need to automate everything & do it all the time.
It turns out that this is what Kent & @RonJeffries @GeePawHill & many other folks have been nattering on about & being broadly misunderstood. @KentBeck has some brilliant essays (scattered across FB & his site alas) & @GeePawHill has amazing twitter threads on the topic
When you look at *what it takes* to get to the DORA measures that @nicolefv & team write about in Accelerate, the input metrics for the DORA outputs, it’s making small changes safe.
As an engineering leader, I provide training, tools, mentorship, leadership development, vision, etc. to help people learn the skills needed to achieve those output metrics. And most of those skills are what @GeePawHill might call the skills of making.
Unfortunately many of those skills are deeply counterintuitive & much of the work is as much unlearning as learning. For example, there’s an implicit definition of work as writing new code, or even writing code.
Because that’s what engineers love to do, and because there are emotional and sometimes financial incentives to make customer visible functionality, we need to overcorrect sometimes on focusing on the tools of making.
Providing visibility & reward for the people who build the CI/CD tooling or build a deployment pipeline that automates acceptance testing, or figure out how to do AppMesh with Terraform as a module or automates linters & code coverage tools in the pipelines.
Great teams end up spending most of their time building user facing functionality because they build the tools of making and sweat automation, IoT, design, architecture, code quality & test automation. Less successful teams try to write lots of code & get stuck.
More from Twitter
Inside: Privacy Without Monopoly; Broad Band; $50T moved from America's 90% to the 1%; and more!
Archived at: https://t.co/QgK8ZMRKp7
#Pluralistic
1/
This weekend, I'm participating in Boskone 58, Boston's annual sf convention.
https://t.co/2LfFssVcZQ
Tonight, on a panel called "Tech Innovation? Does Silicon Valley Have A Mind-Control Ray, Or a Monopoly?" at 530PM Pacific.
2/
Privacy Without Monopoly: A new EFF white paper, co-authored with Bennett Cyphers.
https://t.co/TVzDXt6bz6
3/
Today, @EFF published "Privacy Without Monopoly: Data Protection and Interoperability," a major new paper by Bennett Cyphers and me. https://t.co/Ma2FE2vZ9u
— Cory Doctorow #BLM (@doctorow) February 13, 2021
1/ pic.twitter.com/RzCkQdQRxy
Broad Band: Claire L Evans's magesterial history of women in computing.
https://t.co/Lwrej6zVYd
4/
One of the most Monkey's Paw things about my life is my relationship to books. When I was a teenager, I read all the way through the school and public libraries, spent everything I had on books, and still couldn't get enough and dreamt of more.
— Cory Doctorow #BLM (@doctorow) February 13, 2021
1/ pic.twitter.com/Lgkdk5a7YA
$50T moved from America's 90% to the 1%: The hereditary meritocracy is in crisis.
https://t.co/TquaxOmPi8
5/
Inequality requires narrative stabilizers. When you have too little and someone else has more than they can possibly use, simple logic dictates that you should take what they have.
— Cory Doctorow #BLM (@doctorow) February 13, 2021
1/ pic.twitter.com/BUFyq9H2n4
Many have piped up with commentary and criticized the mix of religion and politics. A convention long held in Canada.
As a Priest and Bishop-Elect, I\u2019d ask that the UCP send Christmas greetings without the wholly inappropriate inference of divine sanction for their government. There are so many things wrong with their use of these words from the Prophet Isaiah it\u2019s hard to know where to start. https://t.co/rwOxVzvnI5
— Anna Greenwood-Lee (@AnnaGreenwoodL1) December 27, 2020
The quote is often repeated at Christmas. “A child is born...” makes reference to the birth of Jesus. Makes sense.
But what does it mean?
Christians (and other religious observers with their religious texts) have made an art form out of interpreting what passages mean.
To those most radically devout (some might say zealously faithful), hidden divine meanings are gleaned from “correctly” reading the bible.
That’s what Dominionists believe. That god himself wrote the bible. Through inspiration of the actual authors, & only they can interpret.
And thus, the “inerrant“ bible serves as a strict road map to save ones soul.
Many devout Christians view the passage as a prophecy made centuries before the birth of Christ. A promise made by god through one of his prophets. Jews interpret the passage very differently.
The Anglican Priest is (obviously) correct about this being supersessionism, and a form of Anti-Semitism.
Troublesome as it is for a Canadian provincial govt to be tweeting out Anti-Semitic propaganda, that’s not the only meaning this passage has for Dominionist Christians.