Profile picture
, 7 tweets, 4 min read
My Authors
Read all threads
one of my favorite things about having a blog is occasionally sifting through all the interesting pieces that link back to mine. 🌻

@shaunabram breaks down a bunch of the skills that add up to managing a team (but can be practiced by any engineer): shaunabram.com/so-you-want-to…
Taylor Murphy recaps his time managing the @gitlab data team. He interrogates his personal struggles with a touching frankness as well as delivering solid advice on the technical front. More stories like this one, please. 🌷

gitpossible.com/lessons-learne…
this may be one of my favorite pieces of 2020, judging by the shit-eating grin on my face as I read it: a thoroughgoing doomsday investigation into recreating your entire infra from scratch using Terraform and AWS, by @vonfreud of SignalAI. 🤘💥

fmarques.org/disaster-recov…
i liked this piece for its description of senior engineers vs principals, and for its reminder that not every job is for every person. areyoupop.com/how-to-break-t…

it's really hard, as humans, to untangle growth and personal development from "climbing the nearest hierarchy".
this one linked to my piece on why shipping software should not be scary; turns out it's a treasure trove of resources on EVERYTHING. product, strategy, managing, emotional intelligence, execution ... there's like a month of good reading here. 💫whoa💫

theproductmanager.com/topics/the-pro…
a rad slide deck from @kathleencodes on how to keep your technical skills sharp as a manager (without annoying your team), and why you should invest in yourself and your future. i found this one via @shaunabram's piece, i think.

slideshare.net/kvignos/how-to…
and @lunivore on running pre-mortems, or "futurespectives". this is one of my favorite interview questions for seniorfolk. "it's 2021, everything's in flames, you are ruefully shaking your head thinking you should have known because of ... what?" 🤨

lizkeogh.com/2018/09/12/how…
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
This is a fun and informative thread on matters such as progressive deployments, serverless, canaries, and chaos.

And at least one useful point I don't think I've ever thought to articulate before, along the subject of testing in production ...
... which is that canaries are useful for testing code correctness and perf of the service itself, while rolling upgrades are useful for testing the impact of your changes on other services or storage systems.

You really want the ability to do both, as someone shipping code.
Actually, this is a great example of sociotechnical problemsolving.

Are you frustrated by too many failed deploys, or days elapsing before bugs are noticed and reverted? Do you struggle with people getting paged and losing time debugging changes that weren't theirs?
Read 14 tweets
Profile picture
Charity Majors
@mipsytipsy
yay, we've beefed up the honeycomb Free Plan -- and you can now sign up for it directly, without going through a sales trial! @fishmegs has a post on why this is so philosophically core to our mission: 🐝❤️ honeycomb.io/blog/free-as-i…
specifically, we added to our free tier the ability to search and sift through your query history -- *and* your team's query history. the grooves you have worn into your system.

this is an aspect of observability that seems to get short shrift; we learn by observing each other.
that's why i'm digging @cyen's stroll down memory lane, with its reminder of some of the principles we baked into honeycomb from the start --

honeycomb.io/blog/sharing-c…
Read 5 tweets
Profile picture
Charity Majors
@mipsytipsy
Reading this thread and having two main thoughts:

1) wtf is a production feedback cycle? I thought that's what being oncall *was*? you're throwing in a ton of extra words that leave me way more confused than I was to start with. 😣

2) well, this is progress.
Five years or so when I started talking about this regularly, I got some of the most vicious replies of my career. We've come a long way since then towards broad acceptance of the core principle: developers should support their code in production, and that means feedback loops.
I never understood "developers should be on call" to be mean "every engineer should carry the pager for an equal number of hours, day and night". on call is about crafting and curating feedback loops, that's all.
Read 9 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!