• About
  • Giving Back

aclairefication

~ using my evil powers for good

Tag Archives: DevOps

Preparing for Winter

05 Tuesday Nov 2024

Posted by claire in Context, DevOps, Experiences, Experiments, Reliability

≈ Leave a Comment

Tags

DevOps

I recently discovered a delightful niche celebration called Fat Bear Week. More than a million people voted for the final contest this year to crown winner Queen Grazer. Leading up to the final vote, many members of the community campaign for their favorite contenders, highlighting their different strengths and achievements. As a newcomer, I appreciate their posts with various kinds of analysis about the bears’ risks and coping strategies as they all try to solve the same problem: readiness for the months ahead.

To begin, park rangers highlight bears for the Fat Bear Week bracket. Some of this has to do with which bears are engaging in the parts of the park that are monitored; after all, this is a participation sport for all the fans. While some fans are engaged months ahead of time, others come to the party at the end for the last week of the season. I’m sure you’ve seen a variety of risk profiles for your applications and your contributors. I like to think of a particular company’s suite of applications as balancing resources with the needs of the whole portfolio as we iterate toward improvement.

We can take lessons from these natural preparations:

  1. Learn from Failure
  2. Prepare for the Unexpected
  3. Prioritize Health

“You take care of what you love, and when you observe it enough you fall in love… the more you connect.” – Charlie Annenberg, Explore.org re: bearcams

Learn from Failure

Year over year, having data to go on helps us to see our continuous improvement, just as it helps long-term bear watchers to see the ongoing story of bears as they survive and thrive. Not all bears survive or thrive, and an analysis of this season’s bear tragedies and conflicts is inherent to studying the brown bears of Katmai National Park and Preserve. Human behaviors like feeding the bears or driving in bear territory can lead to failures for the bears as well as heartache for the people in the park and bearcam watchers. Conflicts among bears are a part of nature and knowing about those aspects of bear life helps people to appreciate the survivors. (Yes, we know bears gonna bear, but it’s still a lot to bear when you see it live.) Despite loss, the community celebrates the successes those bears had and their legacy for the Katmai bears who continue, with a new generation of bears taking over at Brooks Falls this year.

During this emotional outpouring, my first visit to this world of bearcam devotees included hearing some community members wish to preserve the experience of knowing bears for years versus attracting new fans who don’t have that context. Long-term viewers felt that newer viewers didn’t appreciate the history behind the losses so that they might seem trivial. I believe both long-term experience within the context and fresh perspective can bring value to our conversations about what we’re focused on, whether that’s software systems or bears. Hearing what has worked in the past gives me options about how to judge the present situation that intermix with my new ideas as an outsider. I see many of my skills from earlier roles as portable to reliability engineering, and that overlap points me to the alignment of our preparations with the overall goals of teams and the organization. Experts are invaluable in these conversations.

Prepare for the Unexpected

In their chats, interpretive rangers or ranger naturalists “interpret natural and cultural history to help people understand and appreciate the significance of national parks…. with education and interpretation related to the world-famous bearcams.” Watchers can submit questions for experienced professionals to discuss and answer. Reminds you of some remote working knowledge shares you’ve seen, right? Done well, a docent’s remarks can inspire action and bring up different ideas for investigation. While we bearcam viewers at home may not be running experiments with the animals, we’re definitely considering different ways to judge the animals’ weight gain, incorporating the various data sources into our discussions as we cheer our favorite bears. (Terrestrial Lidar?! Yes! Yes! and Yes!) I get similar value from hearing experienced industry colleagues talk about how they have faced problems and the solutions they’ve implemented to address the challenges. Looking for similar risk factors or application characteristics helps me to form experiments when adopting different practices. Will these practices be “best” in a context-free sense or are they optimal for a particular kind of problem that we face (e.g., a peak event)?

For the bears, hibernation season is the time to survive, and all their preparations are tested to the limits. For retail technologists, there are annual events that tend to coincide with other retailers in the industry, e.g., the heavily advertised holiday season. (Did I really go pick the bones of the Halloween crafts right next to aisles of Christmas trees and decor? Yes, yes, I did.) That test of our technology systems and business readiness is most visible during peak business events, when we take extra precautions and think carefully about the unexpected impact issues can have on systems. While we prepare year-round to have our systems stand up to the needs of the market, our routine incorporates seasonal variations designed into our business cycles. We prioritize the most urgent and important work that will support our success.

Prioritize Health

Prioritization. Bears are masters. Limited resources to devote to the crunch time leading up to their goal result in instinctive decision-making. They focus on bulking up at the expense of most everything else, although the mama bears have a juggling act of feeding and protecting cubs as well. As a mama bear myself, I identify with that struggle to focus while also staying aware of my surroundings and changing circumstances to be ready to act, although I’m not likely to be roaring in the face of a competitor like Queen Grazer would do. We develop instincts about our systems over time through experience in running them and familiarity with the people involved.

May we collaborate effectively to have a happily boring (read: peak business as usual) season of surviving and thriving!

And if you love brown bears, contribute to supporting them in Katmai!

Keep your options open

27 Wednesday Feb 2019

Posted by claire in Automation, DevOps, Experiences, Training, Uncategorized, Unconference, Volunteering

≈ Leave a Comment

Tags

CFP, conference, DevOps, event, proposal, serverless, Wardley mapping

In DevOps, there’s a pervasive theme of automating toil, which many would say contains all of testing. I’m just gonna say it: I come from the testing community. We’re people who constantly look for things we haven’t seen yet, who collaborate across roles, who explore the unknown, and who care about doing the right thing. Does that characterization surprise you? Yes, testing is complex enough to be a viable career and not just a thing we do until we can script it for a computer to execute.

So when I reached my limit of “X is going to kill Y” (in this case, DevOps and the testing profession), I finally went for it and joined a DevOps team as an agile tester. I wanted to see for myself that DevOps was the cultural sea change that would make my job role obsolete. If giving up my vocation was the right thing to do, I wanted to be ready with a deep understanding of the value of the new practices and to embrace the mindset shift. I wanted to be ready to bring others along with me on my voyage.

Free electron
Free yourself, electron!

When I attended DevOpsDays Atlanta 2018, I didn’t know what the community would be like. Sure, I’d helped to review their proposals as part of the program committee, but who would I meet who would change me for the better? It was my first time hanging out at an event for people who might identify as “operators” instead of just “developers.” Would they welcome me, a person without any operations background?

Inclusive collaboration wasn’t just the theme of the conference: attendees and speakers shared their authentic selves and wholly embraced it.

Although my discernment of future direction is ongoing, I see as much diversity of thought in DevOps as in agile. The afternoon unconference was my favorite experience! This format is less structured, as you might expect from the name, allowing for free-flowing conversations that address the most current burning questions of the attendees. I found operators wrestle with similar collaboration conundrums. My questions and concerns found ready listeners and new proposed solutions (in addition to new questions!). This diversity of thought helped to open up my perspective on what is possible.

Collaboration with people from diverse backgrounds and viewpoints is a competitive edge. It’s also the right thing to do. We want to keep our professional and organizational options open. Distinct perspectives provide a greater ability to handle the breadth of competitive situations we face. We need new voices and different perspectives to make change possible.

I’m particularly excited about the possibilities this year in bringing 3 communities together! Whether you’re someone looking to refine your role in the context of today’s accelerating software delivery cycles or just curious about how much DevOps, serverless, and (Wardley) mapping enthusiasts have in common, this year’s event is for you!

Our call for proposals ends February 28th (that’s today, procrastinators!), so there’s still time to share the unique experiences that only you can bring, whether through a 30 minute session or a 5 minute ignite talk. If you prefer to attend and then propose topics on the fly like I do, the afternoon unconference provides that space for emergent value.

Let me assure you that constant learning isn’t easy! Change is hard – and worth it. I expect the supportive environment I’ll find at DevOpsDays Atlanta / serverless days Atlanta 2019 / Map Camp 2019 is exactly what I need to just keep swimming. We could all use some help staying afloat.

♣ Subscribe

  • Entries (RSS)
  • Comments (RSS)

♣ Archives

  • November 2024
  • October 2019
  • September 2019
  • August 2019
  • March 2019
  • February 2019
  • November 2018
  • August 2018
  • June 2018
  • May 2018
  • March 2017
  • August 2016
  • May 2016
  • March 2015
  • February 2015
  • February 2014
  • January 2014
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • May 2013
  • April 2013
  • February 2013
  • December 2012
  • November 2012
  • October 2012
  • August 2012
  • July 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011

♣ Categories

  • #testchat
  • Acceptance Criteria
  • Agile
  • Agile Testing Days USA
  • Agile2013
  • Agile2018
  • AgileConnection
  • Approaches
  • Automation
  • Better Software
  • CAST 2011
  • CAST 2012
  • CAST 2013
  • CAST2016
  • Certification
  • Change Agent
  • Coaching
  • Context
  • DeliverAgile2018
  • Design
  • Developer Experience
  • DevNexus2019
  • DevOps
    • Reliability
  • Events
  • Experiences
  • Experiments
  • Exploratory Testing
  • Hackathon
  • ISST
  • ISTQB
  • Lean Coffee
  • Metrics
  • Mob Programming
  • Personas
  • Podcast
  • Protip
  • Publications
  • Retrospective
  • Scrum
  • Skype Test Chat
  • Social media
  • Soft Skills
  • Software Testing Club Atlanta
  • Speaking
  • SpringOne2019
  • STAREast 2011
  • STAREast 2012
  • STARWest 2011
  • STARWest 2013
  • Tea-time With Testers
  • Techwell
  • Test Retreat
  • TestCoachCamp 2012
  • Tester Merit Badges
  • Testing Circus
  • Testing Games
  • Testing Humor
  • Training
  • TWiST
  • Uncategorized
  • Unconference
  • User Experience
  • User Stories
  • Visualization
  • Volunteering
  • Weekend Testing

♣ Meta

  • Log in

Proudly powered by WordPress Theme: Chateau by Ignacio Ricci.