• About
  • Giving Back

aclairefication

~ using my evil powers for good

Category Archives: Uncategorized

Writing a recommendation

02 Monday Feb 2026

Posted by admin in Uncategorized

≈ Leave a Comment

Years ago, a friend at a conference turned to me and said, “Hey, you know testers. Would you take a look at this list?” Not only did I look at the list, but I knew so many of the 125 people on the list that it was a pleasure to help out with highlighting their accomplishments. One thing I noticed is that people who are fans of another person’s work will often share their positive feelings about it without being specific.

Toward a more robust support

For someone who has no experience with that individual person, knowing about the positive interpersonal interactions is important but not sufficient to make a decision about following up on the introduction. I noticed that some of the testers I knew who others shared were “awesome”, “amazing”, or “fantastic” had tangible accomplishments that deserved that space in this listicle. I ended up spending at least an hour editing and updating content to provide more active testimonials for following these community members and to encourage people to engage with them for collaboration, including public speaking opportunities.

When I looked at the article, I saw a lot of effusive praise that the recipients earned and that I also frequently felt for them. However, what I noticed was what wasn’t included. One listed tester was a keynoter, and no one had highlighted that. Another created a framing of problem-solving that helps me. A third wrote a book. And so on.

I’m not writing a listicle today, but I am writing recommendations for my colleagues. Why? I have lost a job before and I feel for them. Even when faced with being let go in a large group, losing a job feels personal and like a critique of the person who no longer has that way to financially support themselves or others.

I’m not an expert on this, but I know how to start. No one has trained me in how to do this correctly. This is just what I do that helps, according to the folks who wrote that article and to people whose work I recommend. Given the recent layoffs, I wanted to share my thinking since we have a great opportunity to support our colleagues who find themselves in a stressful and discouraging position. (I was going to say “tough spot” but that’s not effective in defining and addressing the problem we can help to tackle.)

I’ve been doing this a while, so I just tacitly follow my process. On Friday, a fellow Toastmasters club member asked me how I do what I do, which made me think through what I would recommend. Here’s the list that came out of my mouth. 🙂

emphasizes context, concrete examples, and highlighting transferable skills

I think an effective recommendation emphasizes context, concrete examples, and highlighting transferable skills. Imagine that you are helping your colleague or friend to prep for an interview where the interviewer asks, “Can you tell me about a time when you X?”

Since the job seeker may not know ahead of time what positions are open, I try to make the recommendation easy to understand, not context-free. Context of the work experiences matters a lot and helps to illustrate how potential employers can understand the relevant abilities of my friend or colleague to their work situation. That helps a person to see why this person is a good candidate.

Now, I haven’t tackled the AI screening process, but I assume we have an SEO kind of problem to solve here with keyword inclusion for automated scanning – or even human searching. I would expect to see job listing content injected into applications for a given position, possibly with customized resumes for the job listing. That’s a whole separate part of the problem, so I’m going to leave it at that for now and go back to my recommendation of a person.

Since most job listings I’ve seen in the software industry talk about specific technology stack or technical skills, I try to include those without making my recommendation into a repetition of the resume or a list. I work them into the concrete examples of my direct work with someone so that it’s clear this isn’t just interest or curiosity but actual hands-on experience on the job. If there are measurable results, even qualitative ones, then I recommend you include those. That might require consulting the candidate you’re recommending to get the right numbers or to fact check your claims. I think that’s fine. I don’t think a recommendation has to go sight unseen until publication. I’d much rather get the statements corrected ahead of time.

If you know what the person you’re supporting is looking for next, then tailoring the content to the intended audience, such as recruiters and hiring managers for a specific company, is helpful.

When I worked in testing, someone introduced me to the heuristic framing of What? So what? Now what?
In this case, the now what is definitely consider this person for your job opening. That leaves the what and why to care about the examples. The “so what” is the significance, so be sure to work that into the examples of what you observed on the job while working with someone.

This is by no means a complete rubric, but I wanted to get this out there for folks who are having trouble starting. There’s no wrong way to start! Get your thoughts down and then get another set of eyes on it to see whether it’s helpful. If you know someone who can give feedback other than the candidate, even better! Feedback is a gift, even if what you hear is there’s more work to do.

Time to automate the boring stuff

17 Saturday Jan 2026

Posted by claire in Uncategorized

≈ Leave a Comment

Timekeeping is not my strong suit. I know time exists. I just don’t notice it passing. This is most obvious when I’m in the midst of a good book and I look up to notice it’s 1 AM and I’m quite late for bed.

My Toastmasters club finally convinced me to take on the dreaded job of Timer yesterday. One of the things we do in the club is stretch our skills to develop them, so this is definitely one of those times when I confront my weaknesses and think through the next small step to improve.

Now, the day after the meeting, I’ve finally looked up the official role description. I didn’t need to know the details exactly because the purpose is clear: we’re practicing timeboxing. Monitoring the metric using technology and reporting out on it isn’t the hard part: it’s the other piece “listen carefully to each participant and signal them accordingly.”

For me as an audience member, getting caught up in the enjoyment of a speaker’s topic is the highlight of hearing a talk. I love to see what people are passionate about – or how they respond with extemporaneous remarks to a Table Topic. (Yes, that was our word of the day for yesterday’s meeting. If only I could recall it to use it during my free responses in real time!)

Toastmasters meetings are designed with a specific format in mind [PDF] that prioritizes time management. The agenda often includes Table Topics, prepared speeches, evaluations, and role reports. Each segment has a separate purpose with its own rules.

For someone who wants to focus deeply on the content, being tasked with the structure drives me to think about automating the “boring stuff” (see also “real work” vs “bureaucratic silliness” podcast with Tim Ottinger, which I should really turn into a blog post – noted). I noticed the remote meeting software had built-in timer functionality and decided to experiment with it. Fortunately, we had a smaller group yesterday and there was a bit more room in our timebox to try it out.

As a result of adjusting to the signaling, we had one speaker go over time. We paused the meeting to reflect and I added back posting a colored emoji in the chat at each time interval (i.e. qualifying, getting close to timebox, over time, and grace period ended). This allowed subsequent speakers to conform to the timing goals more easily but reduced my personal engagement with the speeches, taking away some of the fun from the experience.

Being laser focused on one part of the work leads to overlooking other parts of the work, which isn’t really news with what we know from collaborative software delivery. I’ll save that aside for another post to come soon!

Outside of the club, I’m also thinking about short timeboxes for speeches in my work as part of the DevOpsDays Atlanta board. We have so many great talk proposals every year and we’re currently sifting through the surfeit to build the conference program – a tough task!

I’m always interested when I see that some speakers can flex their topics either in the Ignite format or a full length talk. The Ignite format fascinates me: 20 slides that auto-advance and then you’re done. Best seen in slide deck karaoke format, in my humble opinion. Another blog post to come.

Unlike other conference formats, DevOpsDays is single track with comparatively shorter talk timeboxes (i.e. Ignites are 5 minutes, talks are 20 minutes). Even our keynotes are short. I think we’ve only had 1 talk go over time in all the years I’ve worked on the event and that’s on me personally. The timeboxed structure is actually an enabling constraint that gives the whole conference a common experience, for the morning anyway.

Unlike a Toastmasters meeting, the DevOpsDays afternoon open space sessions allow for free-flowing conversations with minimal structure. Yes, I’m an open space devotee, which is another aside I’ll split to a subsequent post. I’m building up quite the backlog as we speak.

While the overall DevOpsDays event is timeboxed, the sessions can flex and attendees can choose their own adventures. (I just got one of those books and have been enjoying finding all the paths. I recommend this vintage pleasure.)

I consider the afternoon a great chance to unpack the morning monotrack content or to pivot to whatever satisfies your curiosity. Last year, I had fun running an open space session based on a mashup of 2 keynotes. Every attendee has a chance to do the same.

I’ve spoken at big multitrack events many times and I always appreciate the folks who provide a heads up about timeboxes expiring, which first really came to my attention at PSL 2014 (see Problem Solving Leadership for Weinberg‘s wonderful legacy). Timekeeping is a great value-add to any session and we can use folks with this skillset to volunteer at our event – hit me up! Seasoned speakers have flexibility in their talks and can adjust to wrap up when the signal cuts through the noise.

That was the challenge we collaboratively overcame at Toastmasters this week: finding the signal without losing the flow.

Giving yourself a chance to experience these various formats as a speaker and participant broadens your knowledge of communication styles while allowing you to focus on leaving the boring stuff to the technology.

And I hope to see you this year at our DevOpsDays Atlanta 2026 event!!

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.

Agile ATL Links

29 Thursday Nov 2018

Posted by claire in Uncategorized

≈ Leave a Comment

Some updated references for my Everything You Wanted To Know About DevOps But Were Afraid To Ask presentation from tonight:

Cross-functional teams in DevOps

Staying-with-the-problem-as-a-service

DevOps practices in the context of agile practices

As well as the previous references from my Agile2018 version of the presentation

https://twitter.com/aclairefication/status/1068343723803717634

♣ Subscribe

  • Entries (RSS)
  • Comments (RSS)

♣ Archives

  • February 2026
  • January 2026
  • 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.