Profile picture
Charity Majors @mipsytipsy
, 10 tweets, 2 min read Read on Twitter
lots of interesting responses to my tweet on code as liability. let's clear a few things up.

first, liability doesn't just mean "thing that causes problems". the primary definition is actually "thing you are responsible for."
if i had my snarky ops pants on, i would ask why such a visceral reaction to the idea of being responsible for your own creations? do they perhaps ... suck to operate?

but i'm a ceo now, i don't throw the easy punches.
for all the people grousing about how green diffs are necessary to move the business forward: believe me, i completely fucking agree.

but you can't clean up the problem by lecturing the people being shit on downstream. it starts at the source: good clean software ownership.
you have to empower your software engineers to understand their code in production, watch it live, poke and prod it. you have to put them on call, so they reap the consequences of what they hath wrought. they have to feel the pain just as viscerally as we do in ops.
not (primarily) because we want revenge, but because this is how things get *better*.

when you give the people with the power and context to make change a portion fo the pain, things *get better*. you won't believe how fast they get better.
have you ever read those magazine articles about people who were born without the ability to feel pain? first you're like "man that would be neat!" then you realize they grow up deformed and horrible and die young.

some pain is a *necessary* feedback mechanism for growth.
good pain: "OW that stove was hot hot hot" i will snatch my fingers away before they burn

bad pain: "OW this dentist drill is hurting me why are you drilling it into my leg why am i strapped down and unable to move what is this dream owww"

^^ a parable
the moral of the story is, pain is a necessary (and deeply minimizable) component of growth. the other components are autonomy, knowledge, and the power to change things.

all developers really need are deploy privileges and good real-time observability for their instrumentation
and monitoring is not observability because it doesn't give you access to the world as experienced from the perspective of the application code.
ok i forgot what i was angry about, i guess that means this thread has petered out into me shaking a cane at the world again
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Charity Majors
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member and get exclusive features!

Premium member ($3.00/month or $30.00/year)

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!