Profile picture
Charity Majors
@mipsytipsy
, 3 tweets, 2 min read Read on Twitter
If you are at #SREcon19 and would like to see a real @honeycombio demo, come our booth around 3:25. ☺️🐝🌷

(May as well just bring by *all* your questions about observability, monitoring, distributed systems and "‘.’
(Oops, wrong tag -- thanks @lizthegrey!) Dear @SRECON kittens, if you want to see a demo of all the shit I'm always going on and on about wrt logging, data, debugging, collaboration etc etc.. come to our booth at 3:25. 📈📊🦠
ooohh and if you have a copy of mine and @LaineVCampbell's book, I have stickers to fix the cover: #srecon
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!

Related hashtags

#SREcon19 #srecon

More from @mipsytipsy see all

Profile picture
Charity Majors
@mipsytipsy
"In general the faster you can react the less up front testing you need." Yep.

Almost every org I can think of could stand to reallocate 20% of their eng cycles away from pre-prod testing towards faster, safer deploys (or post-prod validation).
(The one possible exception that springs to mind is @IntercomEng. Last I heard, it took something like 25 sec to run all tests, package and deploy their 🍒RUBY APP🍒)

You only get that after years of dedicated attention, ofc... & pointing @honeycombio at your build pipeline 😉
You cannot prevent failure. Things are failing ✨right now✨ and you have no clue.

Expect it, budget for it, build your system to tolerate lots of it. Fail fast and fix faster. That's where most of you should be spending your scarce engineering cycles.
Read 3 tweets
Profile picture
Charity Majors
@mipsytipsy
Hey, I would *love* to read some first person accounts from software engineers on learning to support their own code or even just dipping toes into prod. What did you learn? What advice can you give?

Will signal boost if you link me your story. 😊🌈
Sometimes people ask me how they can round out their career/become publicly known as an expert.

My advice is always, look for an emerging trend with a hungry audience, and start learning & talking. Observability is one of those, engineers-in-prod is picking up steam as another.
Nobody really knows what they are doing, and if you just write regularly on what you learned, share code snippets, and interact with other curious early adopters -- it's pretty easy to make a name for yourself.

People will always listen if you are helpful to them.
Read 6 tweets
Profile picture
Charity Majors
@mipsytipsy
A couple great questions came out of the #NYCK8S meetup on Thursday! (Terrific meetup, btw, absolutely stellar crowd.)

First one: what about high security environments, developers can't really go plumbing around in prod willy-nilly like that, can they?!
Answer: hellz yes they can! Developers must be able to own their code in production. No exceptions, just many excuses. ☺️

First of all, if your needs are so high, your super secret shit should not be cropping up in operational data! See lengthy thread:
There are tons of ways to abstract secure data from ordinary operational access patterns. Encryption at rest, wrappers and audit logs, yada yada.

But as @lizthegrey points out: all the regulations really require is a two-person protocol.
Read 4 tweets

Related threads

Profile picture
Liz Fong-Jones (方禮真)
@lizthegrey
Final speaker of #SREcon: @deniseyu21 on why distributed systems are so hard.
@deniseyu21 She's an engineer on PCF, and also an avid artist and live-doodler of talks.

four things for today: a brief history lesson on distributed systems, CAP theorems, why networks partitions are hard/omnipresent, and how we can mitigate these risks. #SREcon
Once upon a time, everyone used a singular database that IT maintained.

But eventually IT became a business enabler we had to invest more in. Business analysts wanted to ask more complex questions, ML/NLP came along, and our requirements increased complexity... #SREcon
Read 18 tweets
Profile picture
Tammy "buttons" Bütow 💀🖤
@tammybutow
Track 1 today @ #SREcon :

SRE Classroom - How to Design a Distributed System in 3 Hours

Ryan Thomas, JC van Winkel, Phillip Tischler, and Jennifer Mace, Google
Requirements:

Identify SLIs and SLOs
▪️Data freshness
▪️Availability
▪️Latency

Sample SLO: 99%ile of queries returns valid result within 100ms

#SREcon #SREclassroom
One way to scale is via microservices.

#SREcon #SREclassroom
Read 24 tweets
Profile picture
Murali Suriar
@msuriar
And now we're with: @JarenGlover on "Tackling Kafka, with a small team" #SRECon
For 3 years, "small team" is me.

Robinhood: democratising access to the financial markets. Saved $$$$ in customer commission fees already. #SRECon
This is not an authoritative talk; it's about providing context so that hopefully you avoid some of the pitfalls I ran into.

Organisational changes, technical evolution. #SRECon
Read 22 tweets
Profile picture
Liz Fong-Jones (方禮真)
@lizthegrey
Over to the streaming/kafka track for a topic I'm very interested in: how other teams run streaming logging/events services on Kafka, by @drkrab #qconlondon
@drkrab [ed: it's going to be interesting to find out whether this is describing their inner design and challenges/pitfalls, or whether it's about their log aggregation product.]

They think that people should log *everything* without sampling. [ed: and I agree, for 24h] #QConLondon
In an error situation, you want to be able to find things instead of having regrets that you didn't index.

[ed: this conflates logging to local disk vs centrally *indexing* it. Honeycomb won't be a full logging product, but it does point to where debug logs live...] #QConLondon
Read 37 tweets
Profile picture
Matt Gardner
@nlpmattg
Announcing DROP, a new reading comprehension benchmark that requires discrete reasoning over paragraphs of text. New @NAACLHLT paper by @ddua17, @yizhongwyz, @pdasigi, @GabiStanovsky, @sameer_, and me. allennlp.org/drop.html arxiv.org/abs/1903.00161
I am super excited about this; I've been thinking about this for over a year, and we finally decided to pursue it as our first collaboration between AI2 Irvine and the UCI NLP group. This is a hard dataset that uses complex questions to test comprehensive understanding.
Key idea: use compositional questions inspired by the semantic parsing literature to put together many pieces of information from a single paragraph. You must get _multiple_ structures from the paragraph correct in order to answer most questions.
Read 14 tweets
Profile picture
Liz Fong-Jones
@lizthegrey
Next up in track 2: @_a12k on Bootstrapping SRE and starting culture change. #SREcon
USDS, working on Veterans Administration. Combining organic devops teams from multiple applications into one single shared SRE team. #SREcon
Expanded from a few initial national priorities like healthcare.gov to hundreds of applications across a dozen plus agencies. #SREcon
Read 28 tweets

Trending hashtags

#SRECon #SREclassroom #DevOps #GoodbyeDemocrats #postofficetrial #SREcon #Monitoring #questions #SorryNotSorry #FLYJOHNNYFLY #chaosday19 #srecon #ServerlessDaysBOS #MAGA #GST #POTUS #Demo #EnemyOfThePeople #QConLondon #DeMo #RedNationRising #Real #MOAB #BuildtheWall #Dash2018
Follow Us on Twitter!

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 ($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!