Charity Majors Profile picture
Jan 27 β€’ 9 tweets β€’ 2 min read
i have a blog post pending on how to tease out the companies who are earnestly trying from those saying all the right things but rotten inside,

but i'll tackle their second question πŸ‘‡ here. how do you know when it's a lost cause, or when you should persevere? 🧡
First: if it's sapping your essence over an extended period of time, just leave. You're no good to us dead.
It's worth persevering through some difficult times when you:

* believe in the mission, that the world is a better place if it succeeds
* have real power to effect change, formally or informally
* can see green shoots, or the wheels beginning to turn, however slowly
and maybe a fourth:

* it should be feeding you in *some* way. developing new skills on the job, learning how to conduct corporate warfare, whatever.

I don't think martyrdom is appropriate for work. You might end up with stale skills and difficulty finding work afterwards.
If you have no real power or influence in the org, or if the more you shout the more people tune you out, just leave. It's not good for you, and nothing you do is likely to matter.

Tell them why you left in your exit interviews. That might help a smidge.
Staying to "protect your people" is not a good reason. I bet half of you are doing this, so hear me out.

If it's a bad place to work, if there's that much you have to shelter them from, you aren't doing them any favors -- you're prolonging the inevitable.
You're preventing them from getting the knowledge they need to get the better job they deserve.

You are ALSO playing straight into the hands of this shitty company and helping them succeed, by retaining labor they do not deserve to retain.
I don't mean to sound harsh. We've all been there. I learned this lesson the hard way. πŸ˜•
Also, just to be straight up honest about it, if you really really need the fat cash for a while longer, you might have to stay.

Just try to be honest with yourself about what "need" really means, since lifestyles tend to expand to match the firehose of cash. Don't get hooked.

β€’ β€’ β€’

Missing some Tweet in this thread? You can try to force a refresh
γ€€

Keep Current with Charity Majors

Charity Majors Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @mipsytipsy

Jan 26
*earn* is the operative word there. you can't just tell your reports it's safe; they're just going to assume you're setting traps for them.

you have to earn it by building trust and creating safety over time. they're paying attention to your actions, not your words.
and part of that means consistently giving them feedback, constructive as well as praise.

*ask* how they prefer to receive feedback. give it gently, give it timely, give with a true spirit of "trying to help each other become better". don't let things snowball into badness...
and *solicit* their feedback for you with equal vigor. solicit often, receive it gracefully, show that you heard it and are making changes.

trust is built in part by being willing to say awkward things, by showing up to discuss the hard things with care and sensitivity.
Read 4 tweets
Jan 26
if you are working at a place where you are being actively mistreated, i actually think you have a moral responsibility to leave (if you can do so).

caveats abound, of course.. it is not YOUR job to fix shitty companies, many are not fortunate enough for this to be an option, &c
but companies are out there feeling complacent about their employees and blind to their pain. i guarantee you nearly every leadership team is like "this is a great place to work" *pats self on back*

by staying, you vote with your feet and your labor for shitty companies to win.
when people start leaving and being straight up with their leadership teams about why they're leaving, it's one of the only things that can shock a company into changing course or trying to do better.
Read 7 tweets
Jan 26
when someone turns in their notice, you should not respond with:

πŸ„ silence
πŸ„ stony stares
πŸ„ retaliation
πŸ„ pressure
πŸ„ guilt tripping
πŸ„ ignoring them
πŸ„ failing to meet their eyes
πŸ„ saying "we're better off without them anyway" TO ANYONE

-- my subtweet of the day
if you really are better off without them, that's a problem with *your* managers, not their fault. saying so is sour grapes, and making it about them inappropriately.
if you loved working with them, by all means tell them how much you will miss them, and you hope to work with them again someday! this is a small industry, and you very likely will.

don't leave them with a lingering sour taste about you.
Read 14 tweets
Jan 17
This is exactly what we have to overcome. Shipping code with instrumentation, then looking at it, is what makes development FAST, EASY, and FUN.

I agree that the tooling has been too opaque, unnatural, focused on systems instead of lines of code. But this is *changing*. Fast.
Once someone has experienced how much easier it is writing code with real observability, you cannot pull it out of their cold dead hands. It's like getting glasses for the first time, and realizing you could barely see the world around you.
This is partly a generational thing. Those of us who grew up writing software with metrics and logs have a lot of unlearning to do, a lot of trauma and frustration to unwind.

Engineers who never learned to navigate monitoring tools actually have it much easier picking up o11y.
Read 4 tweets
Jan 15
I would actually argue that, with the right tooling, production is *exactly* the most effective place to take chances, make mistakes, and get messy. πŸ™ƒ Otherwise you're like this guy.
Here are the slides for a talk of Liz's that I modified slightly and delivered on Wednesday for the O'Reilly InfraOps superstream. speakerdeck.com/charity/observ…

We walk you through the honeycomb backend, some of the ways we perform chaos engineering, and some infamous outages,
to show just how swiftly, accurately, and powerfully you can manipulate systems with modern tooling (feature flags, fast delivery, superb observability) and do whatever the fuck you want in prod without hurting your users.
Read 9 tweets
Jan 15
LARGE SYSTEMS USUALLY OPERATE IN FAILURE MODE, via @dangolant

Or like I used to say, your distributed system exists in a continuous state of partial degradation. There are bugs and flakes and failures all the way down, and hardly any of them ever matter. Until they do.
This is why observability matters. SLOs make large multitenant systems tractable from the top down, but observability makes them comprehensible from the bottom up.
Maybe only .001% of all software system behaviors and bugs ever need to be closely inspected and understood, but that tiny percentage defines the success of your business and the happiness of your users.

And you CANNOT predict what will matter in advance.
Read 8 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


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

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

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

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(