, 16 tweets, 6 min read Read on Twitter
Next is @tmclaughbos on what happens when the server goes away! #ServerlessDaysBOS
@tmclaughbos Serverless DevOps -- citing @alicegoldfuss on the difference between what we're taught in school to do with turing machines vs. what we actually do: shoving protobufs between services #ServerlessDaysBOS
People worry about being replaced and being no longer qualified for their jobs when you start talking automation, devops, etc.

But yet we hold in our hands the solutions to so much pain because of operationally inexperienced teams. #ServerlessDaysBOS
And there's the simple things, like configuring replication on Cassandra, and more complex things like setting CloudFormation properly to not accidentally delete your data. It won't save your data unless you *name your tables*. You have probably messed this up. #ServerlessDaysBOS
Where does operations belong in serverless? "Get rid of your ops team."

"Tear down the silos..." doesn't quite work in practice. We already have full stack delivery teams.

Don't play tollbooth operator. #ServerlessDaysBOS
Leave functionally aligned teams and join the value delivery teams. The ops *teams* go away but your skillset is still useful. #ServerlessDaysBOS
Use actual data from instrumentation and loadtesting to decide which architecture is more performant and cost-efficient rather than arguing in circles. #ServerlessDaysBOS
Making purchasing decisions often winds up being an ops decision.

Operability winds up being useful to design into systems from the start e.g. adding dead letter queues, alerting, etc.

But we also need to code. #ServerlessDaysBOS
You have to be able to code. [ed: and product engineers need to be able to operate too, kinda sick and tired of seeing exhortations for ops to code and not dev to ops]

We need to write load generators, retry frameworks, etc. as operators. #ServerlessDaysBOS
Bugs do not necessarily manifest in one place; data generation vs. validation vs. usage can be scattered across service boundaries.

Run game days. Be prepared at 3am. [ed: called out, was only one who raised hand].

Who actually does chaos engineering? #ServerlessDaysBOS
[ed: @GremlinInc is making it easier to do without being an expert now! they have a community edition product now!]

Shift left to product; add value by reducing toil and spend newfound time on what we're building/why instead of adding shiny tech. #ServerlessDaysBOS
Talk about growth metrics with your product teams. Do you know what scale you're designing for, or are you winging it? More scale is not always better. #ServerlessDaysBOS
and do you know how application performance corresponds to user happiness? Do you know what good enough means for your application? [ed: e.g. having SLOs that are truly customer-centric]

Are you chasing service objectives that aren't necessary? #ServerlessDaysBOS
Making it faster and more reliable has diminishing returns. It doesn't matter if your architecture is designed to support 1M users if it isn't actually capable of attracting/retaining 1M users. #ServerlessDaysBOS
Serverless is just as good of a mechanism for delivering garbage faster and more efficiently to users as it is for delivering value. Pay attention to what you're building. [ed: and also on your impacts on the world! ethics matter!] #ServerlessDaysBOS
Make sure you know about customer success metrics, workload on customer support team, user personas, buyer personas, etc. -- make sure your work has meaning.

Focus least on tech. Focus on what matters: making people happy. [fin] #ServerlessDaysBOS
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 Liz Fong-Jones (方禮真)
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!

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!