#devopsdayshfd search results

Takeaways: spikes were easy to manage in a serverless environment; observability is important to undertand what is happening (invocation times, etc); not everything needs to be serverless. [fin] #devopsdays #DevOpsDaysHFD

Collecting data from lambda functions and ingesting it into datadog needed some creativity - lambdas live for a maximum of 15s, while datadog worked by host. They hit rate limits, and used lambdas on cloudwatch subscriptions in order to get past this. #devopsdays #DevOpsDaysHFD

They're doing most of this using AWS lambda, and needed to deal with various issues as they scaled out from nothing to 10,000 screens all requesting ads. #devopsdays #DevOpsDaysHFD

The billboards themselves request ads when they have slots, and it produces a real-time bidding process to select which ad will be returned to the billboard. #devopsdays #DevOpsDaysHFD

One of the challenges is to programatically control the content that appears in a particular location. Not all ads can appear in all locations (possible legal issues, usefulness, etc.). #devopsdays #DevOpsDaysHFD

Next up: @taqkarim talking about scaling PlaceExchanges platform for streetside screens. #devopsdays #DevOpsDaysHFD

Preparing for on call is important - allocate the mental bandwidth (reschedule fewer high-focus efforts); treat yourself (shedule things you enjoy to counteract the stress of on call). [fin] #devopsdays #DevOpsDaysHFD

We can improve the on call experience. One way to help with this is to create rituals for context switching between going on call and coming off call. Some people have an on-call hoodie, so that they can take it off when they're done. #devopsdays #DevOpsDaysHFD

... control fallacies (no control / total control illusions). These are all causing us to see the world _differently_ than it actually is. #devopsdays #DevOpsDaysHFD

We need to be aware of and deal with cognitive distortions - for example, polarized thinking (all or nothing thinking), overgeneralization, fortune telling (assuming data can predict the future, analysis paralysis)... #devopsays #DevOpsDaysHFD

But the process has to _have a conclusion_. #devopsdays #DevOpsDaysHFD

We need to process our failures to work through trauma events - to integrate them into a coherent whole. Talking it through helps the entire organization. The larger the organization, the more important it is to share our postmortems. #devopsdays #DevOpsDaysHFD

This doesn't eliminate the stress of the 2 am call, but keeps us from getting wound up about the process. More practice helps make it _just part of our job_. #devopsdays #DevOpsDaysHFD

We need to normalize the experience of incident response to keep from getting overwhelmed and deregulated; game days should be a safer context, but need to actually practice our real incident response processes. #devopsdays #DevOpsDaysHFD

Somatic experiencing is a technique for training ourselves to have healthy responses to trauma; we can adapt this to our organizations as well in order to get back to a regulated state. #devopsdays #DevOpsDaysHFD

Part of what we need to do is to identify our organization's window of tolerance (can vary from org to org), so that we can identify when we're deregulated. Resilient organizations are _not_ traumatized by routine threats. #devopsdays #DevOpsDaysHFD

Both of these are inappropriate responses, and prevent us from getting back into the healthy region of the window of tolerance. #devopsdays #DevOpsDaysHFD

Organizations display similar behaviors. Getting stuck on - a hyperarousal state - are super vigilant about everything, and not able to move forward effectively. Getting stuck off - hypoarousal - is also a problem because we can't make changes. #devopsdays #DevOpsDaysHFD

Healthy nervous response operates in a window of tolerance, moving between the sympathetic and paraysmpathetic responses. When we get outside that range, we can get stuck "on" (fight or flight) or "off" (freeze). #devopsdays #DevOpsDaysHFD

Among the differences, we have a prefrontal cortex that can replay traumatic events. #devopsdays #DevOpsDaysHFD

#devopsdayshfd

Hacking your @EmotionalAPI #devops #devopsdayshfd

Woohoo! @chef is also a #DevOpsDaysHFD sponsor! #DevOpsDays

Good morning, #DevOpsDaysHFD!

Up now: “All for Ops & Ops for All” by @odierouth #devopsdays #devopsdayshfd

Psychological Safety and DevOps by @mettamatt #devopsdays #devopsdayshfd

Now: “Change Management for Humans” by @thelongshanx #devopsdays #devopsdayshfd

Thank you @pagerduty for sponsoring #DevOpsDaysHFD!!

Thank you @pivotal for supporting #DevOpsDaysHFD!! #DevOpsDays

Now: “At This Moment” by @johnksawers #devops #devopsdays #devopsdayshfd #mindfullness

Kicking off day 1 with @jpaulreed #devopsdays #devopsdayshfd

Ignites starting now! Starting with “The Devil's DevOps” by @wiredferret #devopsdays #devopsdayshfd

Starting now: “This Lane Ends: Shifting Security Left” by @PeteChestna #devops #devopsdays #devopsdayshfd

Next ignite up now: “Convince Your Boss: Why DevOps in 5 Minutes” by @KSAlbrecht #devops #devopsdays #devopsdayshfd

Up now: “What Containers Don’t Solve” by @mnewswanger #devops #devopsdays #devopsdayshfd

Ignites starting now: “Checklists: Good Enough for NASA, Good Enough For Your App!” By @jaydestro #devops #devopsdays #devopsdayshfd #devops

Thank you @CyberArk for sponsoring #DevOpsDaysHFD!!

Learning from Wildland Firefighters by Alan Kraft #devops #devopsdays #devopsdayshfd

Kicking it off today: “Every Scar A Story” by @wiredferret #devops #devopsdays #devopsdayshfd

#DevOpsDaysHFD is happening thanks to great sponsors like @opsgenie!! #DevOpsDays