Profile picture
, 3 tweets, 1 min read
My Authors
Read all threads
oh no, consider yourself fully adopted and endorsed. the observability gap is real, and consists of

- data not gathered, or
- improperly stored,
- inflexible UX,
- inaccessible questions (for devs),
- inaccessible instrumentation (for ops)
- deploy policies
- curiosity
A huge part of the observability gap is the way our tooling presses us /hard/ to jump straight to answers, instead of comfortably, playfully lingering and iterating in the realm of questions.
Think of the engineer staring at her "single pane of glass" dashboard and trying to understand her complex system by thinking really, really hard.

It's the ops version of trying to debug your software by reading the source code.
Missing some Tweet in this thread? You can try to force a refresh.

Enjoying this thread?

Keep Current with 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!

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!

More from @mipsytipsy see all

Profile picture
Charity Majors
@mipsytipsy
Years ago, at Linden Lab, we struggled to share tribal knowledge about production, and many engineers were terrified of touching prod (esp new hires)

Enter Shrek Ears. Anyone who broke prod would wear the Ears the rest of the day. I know; sounds awful. ☺️
It wasn't. If people saw you wearing the Ears, they would ask you eagerly for the story -- what happened?! How did you find it, what was the fix? -- and regale you with their own stories.

It was socially leveling -- you'd see the senior engineers sporting Ears in good cheer.
If anyone was self flagellating, we could correct it on the spot and say.. we don't do that here. "You did the reasonable thing! How can we make the system better?"

It became a rite of passage for new hires. "Now you are a blooded warrior, now you are truly one of us."
Read 5 tweets
Profile picture
Charity Majors
@mipsytipsy
People overestimate how much of the speed at which they ship software is a function of their own abilities, and radically underestimate how much is set by the systems they operate in. 🤔
Some things that impact your ability to ship swiftly with confidence:

* language, framework, library support
* deploy process and tooling
* on call rotations
* defaults, any+all
* expectations
* cultural scripts around failure
* who is admired? why?
* levels, promotions
Developing software in modern times is like operating heavy machinery. So, so many powerful tools at our disposal. (And thus ops skills are an increasingly critical part of the effective software engineer's toolkit.)
Read 14 tweets
Profile picture
Charity Majors
@mipsytipsy
An interview is not a game of skill, except insofar as your skills may (may!) be what got you in the door.

It's psychologically healthier and arguably more realistic to treat it like a dice game -- one rolled by you, your prospective employer, and the gods of chaos.
I mean, how might you act if you believed interviews were games of chance?

- you would play the numbers, and expect a good outcome given sufficient tries
- you might roll sometimes just to see what's out there
- you wouldn't carry all the dread, shame & aversive baggage around
It's just as good to keep a healthy skepticism about the interview process from the employer's perspective.

every hire is a risk, and if you have invested enough time to feel highly confident in your opinion, you have likely also exhausted the candidate and all interviewers. 🙃
Read 3 tweets

Embed code for your website

×
Follow Us on Twitter!

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.00/month or $30.00/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 Become our Patreon

Thank you for your support!