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

A big part of my tweets are inspired by other people's content.

I bookmark everything that looks interesting and go there when in need of inspiration.

This is a thread-recap of the best-saved tweets from 2020 (for me at least) and what you can steal from each one. 🧵👇


The year chart by @jakobgreenfeld

What to steal: the idea and the design

Create a chart with the key moments of your growth. It's a great reflective exercise for you and it can be a great learning experience for your


Let's collaborate by @aaraalto

What to steal: the idea.

Creating a blank piece of content (could be a sentence, a design, a video...) that your audience can later


Advice to first-time info product creators by @dvassallo

What to steal: the insight

This tweet was one of the sparks for me writing the Twitter Thief ($1,3k revenue says it's good


How to be a better writer by @JamesClear

What to steal: the insight

A world-class writer giving free writing lessons. The tweet is from 2019 but I discovered it this
Here are some of the best threads I've ever read on Twitter,

All related to

- Startups
- Entrepreneurship
- Indiehacker
- Wealth
- Health
- Life nd philosophy

I'll keep updating them regularly

Read below 👇

1. Getting reach without being luck, best tweet ever by


2. On meditation by


3. On college and eduction by


4. "Deep Year" concept by

You May Also Like

The YouTube algorithm that I helped build in 2011 still recommends the flat earth theory by the *hundreds of millions*. This investigation by @RawStory shows some of the real-life consequences of this badly designed AI.


This spring at SxSW, @SusanWojcicki promised "Wikipedia snippets" on debated videos. But they didn't put them on flat earth videos, and instead @YouTube is promoting merchandising such as "NASA lies - Never Trust a Snake". 2/


A few example of flat earth videos that were promoted by YouTube #today:
https://t.co/TumQiX2tlj 3/

https://t.co/uAORIJ5BYX 4/

https://t.co/yOGZ0pLfHG 5/