Discover and read the best of Twitter Threads about #velocityconf

Most recents (19)

as usual, liz's recap is a clear and crispy version of my talk, and you should read it if you're intrigued by the idea of testing in production.

(but I've still got the edge on rainbows muahaha đŸŒˆđŸŒ·đŸ’œđŸ’™đŸ’šđŸ’›đŸ§Ąâ€ïžđŸŒžđŸŒŸđŸŒˆ)
favorite moment of this afternoon was afterwards, when a few -- multiple! -- people with formal security and QA backgrounds came up and told me even MORE reasons to urge testing in prod. đŸ€—đŸ„°
second favorite moment has to be at the end when I was marveling over my own moderation and self-restraint, and @lizthegrey piped up "I'm a good influence!" sotto voce, front and center. đŸ€ŁđŸ„ł
Read 4 tweets
Now up are @editingemily and @nicolefv talking about “Why should I care about DevRel anyway?”
#VelocityConf Image
This is a game show style session modeled after Jeopardy... with gifs.

First question: do you need to be a Twitter celeb?

Nope! It’s great to be able to magnify voices of those that might not have a megaphone. But not essential, some of the best aren’t public.

#VelocityConf
What is DevRel anyway?

@editingemily - I like to think of us as the API between developers and the product team! Also, there’s a lot of talking.

#VelocityConf
Read 10 tweets
Really excited for this next talk by @LauraMDMaguire on “Lowering costs of coordination during service outages: A multiple case analysis”

#VelocityConf ImageImage
@LauraMDMaguire is going to be going into details associated with the research done as a part of the SNAFU Catchers Consortium (snafucatchers.com)

#VelocityConf
@LauraMDMaguire’s engagement with SNAFU actually starts with the tri-can device which is used in rock climbing.

vdiffclimbing.com/tricams/

#VelocityConf Image
Read 27 tweets
First talk on the leadership track is @BethAdeleLong talking about “Having the Bubble: How Experts Build, Maintain, and Spread Deep System Knowledge”

#VelocityConf Image
We are going to focus on the Experts that are using and maintaining our systems.

Why is this important? Experts are the least understood aspects of our systems!

Work by @ddwoods2 and @ri_cook is significant influence in all we’ll be talking about today.

#VelocityConf
What does “Having the Bubble” mean?

It’s from aviation and submarine navigation. It means you’re able to understand the context of your overall situation based on data you have access to... often through tooling

#VelocityConf
Read 12 tweets
Next up, @bobquillin on The Cloud Native Elephant in the Room #VelocityConf Image
A lot has changed over the past decade! How we build, how we operate, where we run our software.

What’s the elephant though? It comes down to people problems.

- Enterprises are slow and getting left behind
- Transistion is starting
- Cloud lock-in is rampant

#VelocityConf Image
@bobquillin is producing a multi-cloud approach to keep our communities open.

We have a few case studies. First is CERN which uses k8s to deploy their tools to keep things portable between public and private clouds.

#VelocityConf Image
Read 3 tweets
First talk up is @lizthegrey talking about Production Excellence.

#VelocityConf Image
If you haven’t read @lizthegrey’s opus on Sustainable Operations, go take a break after the keynotes and read it. Should be mandatory if you own a service or product.

infoq.com/articles/produ


#VelocityConf
What runs our software? People. We need to focus on our people, culture and process.

ProdEx is about making our holistic systems more reliable and resilient. It takes *everyone* to make this happen.

#VelocityConf
Read 8 tweets
Working on getting ready for the “Everything is a little bit broken; or, The illusion of control” talk by @wiredferret.

We are practicing some resilient behavior trying to get a presentation up without the right A/V cables... anyone have a Lightning-to-HDMI?

#VelocityConf Image
And we are good!!!

#VelocityConf Image
Did you know that Airplanes have an error budget? There’s a level of acceptable “failure” or lack of maintenance allowed prior to a plane being grounded - even if it’s just the overhead storage latch failing.

#VelocityConf
Read 9 tweets
“Observability for developers: How to get from here to there” with @cyen!

#VelocityConf Image
We are talking a bit about the Dev/Ops wall and @cyen’s experience of developing *so* fast... and how that sometimes turns into the stereotype of devs breaking things.

#VelocityConf Image
Unsurprisingly, one of the biggest triggers of of incidents is the act of generating change.

m.subbu.org/incidents-tren


#VelocityConf
Read 8 tweets
Afternoon talks starting with @aaronrinehart on “Security Precognition - applying chaos to security” #VelocityConf Image
First, what’s Resilience and how it applies to Chaos? Resilience is all about the incident that never happened.

#VelocityConf
We are covering a *lot* during this session... Pictures are worth a thousand words here.

#VelocityConf Image
Read 14 tweets
Last night -- took 4 hours to find my airbnb, which I was locked out of; another 2 he til I got in (at 5:30a)

This morning -- locked in the cement basement for an hour w no signal

... San Jose hates me, your honor, and that's why I'm late for author signing @velocityconf đŸ˜©
let's not even get into last night, where I ended up in a hotel where I picked up my keys from a bulletproof glass window facing the street, and high tailed it home at 3 am after realizing my neighbor was... entertaining visitors, and her pimp outside kept calling to me #sanjose
(that's not even why I went home, actually... went home because there was no AC, and heeeeell no)

Anyway, my book signing will be during my ask the experts session. It's better this way. I'll have some unicorn cover stickers here by then. #VelocityConf
Read 3 tweets
Next up: @jessitron with “From puzzles to Products”

Puzzles are just a stepping stone to the “real work” of your product.

#VelocityConf ImageImage
Puzzles can be well defined problems - products aren’t well defined. They’re an evolution and ongoing dialogue with customers to determine the puzzles needing to be solved. This is further reinforced by puzzles already solved by the “Rest of the World”

#VelocityConf Image
Abstraction and (especially) SaaS is incredibly powerful for companies. You don’t need to “know how to build a pencil to write with it” you can focus on the problems your biz needs to really solve!

#VelocityConf ImageImage
Read 6 tweets
A quick reminder and a thread regarding the @MarriottBonvoy power outage at #VelocityConf:

1) Just because Marriott isn’t a traditional tech company doesn’t mean they don’t deserve #hugops. This has to be just as rough for the employees as the guests

1/n ImageImage
2) #VelocityConf attendees think of this as an awesome opportunity to think through how you would approach a post-incident review for the event. Who would you talk to? What questions would you ask? How would you maintain a blameless culture?

My take continues...

2/n
Who would you talk to regarding the power outage?

There are a few main stakeholding entities involved (that I’ve been able to identify so far):

- Marriott employees and staff
- Guests of the Marriott
- Local power company
- #VelocityConf staff

3/n
Read 7 tweets
"There are only two things your organization should be spending time on: making your customers happy, or making your people happy.". -@lizthegrey at o11y meetup. #velocityconf
"CI/CD is great, and it's only the first step. We need to learn how to get our code into production faster, understand it better, and use the same tools for pre-prod and production"

(my phone camera broke so all I can do is selfies now, sorry)
speaking of which, here is my summary of San Jose today
Read 3 tweets
Aaand we are starting the Ignite session at #VelocityConf MC’d by @nicolefv ! Given the rapid fire talks, going to keep this to a single thread...
Talk on good practices for distributed teams:
1 It’s not about cutting costs
2 Provide autonomy
3 Invest in communications
4 Hybrid teams are ok
5 Don’t lower the bar for off-shore teams
6 You can attract talent from all over Image
Now eventual consistency with @vllry including CAP theorem, eventual consistency, and more! #VelocityConf ImageImageImage
Read 10 tweets
First tutorial of the day: “Move Fast and Learn from Incidents” with @lhochstein , @this_hits_home , and @nora_js along with a great crowd of TAs from Netflix, Slack, New Relic, and OSU! #VelocityConf
We are going to be role playing a few incident investigations during the session #velocityconf
A few things we’ll be looking for during these investigations which @lhochstein deems “gaps” falling into the following categories:
1) Tools
2) Operational expertise
3) Resource (people) gaps

#VelocityConf
Read 13 tweets
@caseyrosenthal starting a discussion on complexity prior to diving into #ChaosEngineering #VelocityConf Image
This is a microservice call knot - it’s what happens when you start to nest service calls. “Why would you want to do this !?” #VelocityConf Image
Transitioning from @plainprogrammer ‘s talk on Accidental Architecture to @caseyrosenthal ‘s talk on Deprecating Simplicity is great - would have been awesome on the same track or recommended as back to back sessions. #VelocityConf
Read 3 tweets
Hbr is Twitter for executives #velocityconf @nicolefv
In 2003 hbr published an article that said IT doesn't matter. In 2009 Flickr demonstrated the opposite. @nicolefv has the research now showing DevOps investment makes business performant #velocityconf
Our intuition told us this was true and now we have the data to back it up. #VelocityConf
Read 13 tweets
Next up at #velocityconf its the one and only @jaqx0r - Google SRE extraordinaire on how best to monitor with SLO’s
The cost of maintenance of a system must scale sublinearly with the growth of the service - #velocityconf

At Google, Ops work needs to be less than 50% of the total work done by SRE
Once you have an SLO that’s really not an SLO since the users have come to expect better, then you’re unable to take any risks. Systems that are *too* reliable can become problematic too. #VelocityConf
Read 9 tweets
The distributed real time telemetry challenge at NS1

- 5-700K data points per sec
- avg of 200K data points per second (terabytes per day)
- why an OpenTSDB approach failed (DDOS attack mitigation required more granular telemetry and per packet inspection)
- why ELK made sense
“Given all the problems we had, we decided that we needed to pick a tool that had a solid community behind it. We wanted to gain from a flourishing community and wanted to contribute back” - why ELk was chosen as a long term time series database at @NS1
openTSDB still wins hands down for analytics purposes but NS1 didn’t need that. OpenTSDB requires deep operational expertise to tune, scale and run which NS1 didn’t want to invest in.

The used the beats ecosystem (beats is the oss project from eBay, iirc)
Read 10 tweets

Related hashtags

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!