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
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
Here's roughly how I grew from 0 to 1400 followers in 4 months. pic.twitter.com/NqY54cWXpC
— Jakob Greenfeld (@jakobgreenfeld) December 15, 2020
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
Let's collaborate
— Aaron Aalto (@aaraalto) December 17, 2020
Step 1: Take this image
Step 2: Be creative with it
Step 3: Reply with your creation pic.twitter.com/xCcCShLvdI
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
My advice to first-time info product creators:
— Daniel Vassallo (@dvassallo) July 26, 2020
1. Start with a very small product.
2. Choose a topic you know well that will almost write itself. Avoid doing research.
3. Timebox production to 2 weeks.
4. Charge $10.
5. Promote it!
All the lessons are in #5. Best of luck!
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
How to be a better writer:
— James Clear (@JamesClear) July 5, 2019
-write about what fascinates you
-make one point per sentence
-use stories to make your point
-cut extra words like \u201creally\u201d and \u201cvery\u201d
-read the whole thing out loud
-post publicly (you\u2019ll try harder when you know others will read it)
What else?
You May Also Like
One thing I've been noticing about responses to today's column is that many people still don't get how strong the forces behind regional divergence are, and how hard to reverse 1/ https://t.co/Ft2aH1NcQt
— Paul Krugman (@paulkrugman) November 20, 2018
See this thing that @lymanstoneky wrote:
And see this thing that I wrote:
And see this book that @JamesFallows wrote:
And see this other thing that I wrote:
Here I will share what I believe are essentials for anybody who is interested in stock markets and the resources to learn them, its from my experience and by no means exhaustive..
First the very basic : The Dow theory, Everybody must have basic understanding of it and must learn to observe High Highs, Higher Lows, Lower Highs and Lowers lows on charts and their
Even those who are more inclined towards fundamental side can also benefit from Dow theory, as it can hint start & end of Bull/Bear runs thereby indication entry and exits.
Next basic is Wyckoff's Theory. It tells how accumulation and distribution happens with regularity and how the market actually
Dow theory is old but
Old is Gold....
— Professor (@DillikiBiili) January 23, 2020
this Bharti Airtel chart is a true copy of the Wyckoff Pattern propounded in 1931....... pic.twitter.com/tQ1PNebq7d