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 đđ·đđđđđ§Ąâ€ïžđžđđ)
(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. đ€Łđ„ł
Now up are @editingemily and @nicolefv talking about âWhy should I care about DevRel anyway?â
#VelocityConf
#VelocityConf
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
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
@editingemily - I like to think of us as the API between developers and the product team! Also, thereâs a lot of talking.
#VelocityConf
Really excited for this next talk by @LauraMDMaguire on âLowering costs of coordination during service outages: A multiple case analysisâ
#VelocityConf
#VelocityConf
@LauraMDMaguire is going to be going into details associated with the research done as a part of the SNAFU Catchers Consortium (snafucatchers.com)
#VelocityConf
#VelocityConf
@LauraMDMaguireâs engagement with SNAFU actually starts with the tri-can device which is used in rock climbing.
vdiffclimbing.com/tricams/
#VelocityConf
vdiffclimbing.com/tricams/
#VelocityConf
First talk on the leadership track is @BethAdeleLong talking about âHaving the Bubble: How Experts Build, Maintain, and Spread Deep System Knowledgeâ
#VelocityConf
#VelocityConf
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
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
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
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
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
@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
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
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
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
ProdEx is about making our holistic systems more reliable and resilient. It takes *everyone* to make this happen.
#VelocityConf
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
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
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
#VelocityConf
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
#VelocityConf
Unsurprisingly, one of the biggest triggers of of incidents is the act of generating change.
m.subbu.org/incidents-trenâŠ
#VelocityConf
m.subbu.org/incidents-trenâŠ
#VelocityConf
Afternoon talks starting with @aaronrinehart on âSecurity Precognition - applying chaos to securityâ #VelocityConf
First, whatâs Resilience and how it applies to Chaos? Resilience is all about the incident that never happened.
#VelocityConf
#VelocityConf
We are covering a *lot* during this session... Pictures are worth a thousand words here.
#VelocityConf
#VelocityConf
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 đ©
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
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
Next up: @jessitron with âFrom puzzles to Productsâ
Puzzles are just a stepping stone to the âreal workâ of your product.
#VelocityConf
Puzzles are just a stepping stone to the âreal workâ of your product.
#VelocityConf
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
#VelocityConf
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
#VelocityConf
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
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
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
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
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
"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)
(my phone camera broke so all I can do is selfies now, sorry)
speaking of which, here is my summary of San Jose today
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
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
Now eventual consistency with @vllry including CAP theorem, eventual consistency, and more! #VelocityConf
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
1) Tools
2) Operational expertise
3) Resource (people) gaps
#VelocityConf
@caseyrosenthal starting a discussion on complexity prior to diving into #ChaosEngineering #VelocityConf
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
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
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
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
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
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
- 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)
The used the beats ecosystem (beats is the oss project from eBay, iirc)
