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.

2/

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.
3/

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.
4/

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
5/

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.
6/

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.
7/

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.
8/

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.
9/

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.
10/

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.
11/

Accelerating teams towards that point where they’ve incorporated the habits of investing in the tools of making & designing architectures that decompose change into very small safe increments is a key area of software engineering management.
12/

Rallying these changes under the flag of DevOps has been the most successful way I’ve seen to describe these habits.

END

More from Twitter

The twitter ban on 45 is a victory in some sense for the immediate but a warning in the long term, not on the curtail of free speech but as gesture towards the expansive power commercial tech has on every aspect of our governance and our lives, I don’t quite have the words but-

What I’m trying to get at, is not just that Twitter’s decision allows us to see—in ways that have been obscured—how much control they have over content moderation—

but as @Elinor_Carmi points out “platforms don’t just moderate or filter “content”; they alter what registers to us and our social groups as “social” or as “experience.”
https://t.co/GSByAOoDWg changed

I’m worried that the celebration of Twitter’s intervention on fascist rhetoric-however too little and too late- directs us to desire tech companies enforcement of liberal and democratic procedures rather than towards an investigation of

how they’ve developed computational infrastructures which exceed the power of the nation state, are hollowing out our institutions for frictionless (see removing human contact) optimization and are insufficiently described by neoliberalism
Today's Twitter threads (a Twitter thread).

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/


Broad Band: Claire L Evans's magesterial history of women in computing.

https://t.co/Lwrej6zVYd

4/


$50T moved from America's 90% to the 1%: The hereditary meritocracy is in crisis.

https://t.co/TquaxOmPi8

5/

You May Also Like

And here they are...

THE WINNERS OF THE 24 HOUR STARTUP CHALLENGE

Remember, this money is just fun. If you launched a product (or even attempted a launch) - you did something worth MUCH more than $1,000.

#24hrstartup

The winners 👇

#10

Lattes For Change - Skip a latte and save a life.

https://t.co/M75RAirZzs

@frantzfries built a platform where you can see how skipping your morning latte could do for the world.

A great product for a great cause.

Congrats Chris on winning $250!


#9

Instaland - Create amazing landing pages for your followers.

https://t.co/5KkveJTAsy

A team project! @bpmct and @BaileyPumfleet built a tool for social media influencers to create simple "swipe up" landing pages for followers.

Really impressive for 24 hours. Congrats!


#8

SayHenlo - Chat without distractions

https://t.co/og0B7gmkW6

Built by @DaltonEdwards, it's a platform for combatting conversation overload. This product was also coded exclusively from an iPad 😲

Dalton is a beast. I'm so excited he placed in the top 10.


#7

CoderStory - Learn to code from developers across the globe!

https://t.co/86Ay6nF4AY

Built by @jesswallaceuk, the project is focused on highlighting the experience of developers and people learning to code.

I wish this existed when I learned to code! Congrats on $250!!