Archive for the ‘shifts’ Category

About that Transition

Inevitably interviewers ask me, How and why did that happen?  – career track shift from environmental science to software development. This question and related blog post by Eric Jacobsen,  You’re a Tester.  How’d that Happen? are fodder for this introspection and retrospection. The Why:  I wanted to be in perpetual state of intellectual challenges, where interpersonal interaction was essential to making tangible positive results happen, and where I could make a better salary.


I chalk the ease and naturalness of this shift up to these things: aptitude, educational foundation in science and engineering, my varied and solid work experience since the age of 14.  The How is below.  Disclaimer: It is entirely possible and likely I would have eventually found what I wanted in the environmental science and civil engineering field as my perspective broadened over time with experience and exposure.


I began to recognize what I wanted a few months out of college and into my role as an environmental microbiologist in a full-service laboratory. I found lab work dull, repetitive and isolating.  My 1st clue that I would eventually love looking for potential problems was when an angry project manager visited me with a complaint; a client was unhappy about their lab results for coliform, biological dissolved oxygen, or cyanide.  The test details escape me, but I keenly remember I felt excited that there was a problem, something to investigate – my lab records. This intrigue was greater than the anxiety which accompanied being yelled at.  I wanted to get answers and help her make the client happy.  My boss, the lab owner, was not excited.  He saw me as unorganized.  There was a bug with the test results on their bugs in a surface water sample.


A college study buddy with the same GPA and degree had gone to work for the technology branch of what was then Anderson Consulting in “Knowledge Management”. When I described what I wanted she said I should look into the company. I decided that if they hired her, then they would hire me.  The corporate office responded to my resume and application with “Thanks, don’t call us. We will call you.” I was undeterred.

As an Auburn Alumni, within 2 years post-graduation, I still had access to campus recruitment events, so I made the drive from Orlando and from Atlanta to Auburn, Alabama, campus for several career events to shake hands with recruiters to make sure they knew my name.  I landed a screening interview followed by 3 more intense behavioral interviews.  Over a year after I had initially submitted my application, I was hired as a “Business Analyst” and spent 1 month in training on C++.  My only prior experience with programming:  1 college Fortran class.  It was no fun.  I felt lost the entire time. Programming became more enjoyable for me in Anderson’s collaborative learning environment and now that I had built a GUI, something with which I could interact!

Sink or Swim

Project 1: I worked night shift, monitored batched script results of database conversion test cycles, followed runbook procedures, and hoped I would not have to call someone if something terrible happened.  Project 2: I used VI in UNIX to write and test conversion scripts for the next phase of the database conversion project.  I had a great team lead and detailed specifications to help me with this.  Project 3: I moved on to a web-based application effort.  I was with a much larger team, and had detailed specifications and guidelines for all phases of testing (V- Model) and also began to test other people’s code.  Magical Project 4: J2EE pilot project at the client site with an architect, a manager and me, the junior developer! Relationships formed, job well done and longer term multiple application contract won. I was always responsible for testing my own code. For the 1st time, I got to work directly with the customer for requirements gathering and elaboration over various UML documents, wireframes, test coverage, and user acceptance testing. Over those 4 years I learned I loved the nature of testing and exploring value with customers and teammates more than I enjoyed coding.  I am grateful for the deliciously diverse approaches, models, and operational processes I continue to learn.

This was and still is wonderful.

Have you ever made a delightful or tough yet satisfying career transition which elicited doubtful questions and puzzled looks from others?  I would like to hear about it!



August and Everything After

Attribution Note:  This post’s title belongs to the Counting Crows album released in 1993.  *Please see below.

One of my software testing community colleagues emailed me this week, “You’ve been quiet.  How are things?”

I went into something akin to recluse mode after an amazing week in New York City in August 2014 where I participated in my first un-conference, TestRetreat2014 NYC with other passionate skilled quality-minded folks, and then participated in three days at CAST2014 NYC where I attended an awesome workshop lead by Noah Sussman, lead a track session (my 1st conference talk, yeah!), and served as LAWST-style facilitator [Ref.] for multiple speakers.  I am an extrovert who thrives on stimulating thoughts and connections in and with others.  I love people, but I also need space and quiet, focus time to recharge my batteries.  My personal goals derived from those energizing days were as follows:

  • TestRetreat – cross-pollinate by talking about software quality to non-testers and kids and engage with local agile or lean software groups.
  • CAST NYC – share my conference experiences (including details on that week) and insights through blog posts.

In keeping with my decompression needs, I had a delayed start plan; I intended to reflect and publish my mix of handwritten and typed notes by pumpkin time, Halloween. That did not happen.  Lesson learned:  Do not wait!  Share your thoughts and reflections while they are super fresh. Yes, I still intend to post insights from over a year ago.  Life happened.

In early October, I took a week long adventure trekking trip with 2 dear girlfriends, and when I returned home I learned that a loved one’s health had taken an alarming nose dive.  Outside of work responsibilities, family, and a 2-room home remodel project prompted by water, shade, and 65 year old plaster,  I did not muster any energy to connect with my software testing community or make a move on my good intentions until awhile after that loved one’s passing in May.

I have slowly been inching out of the woodwork since.  This summer I teamed up with someone locally to transfer leadership of the meetup group I founded, GCST, and to transition it to an agile meetup group.  I started a fresh effort to envision long-term goals and am now preparing and reviewing course materials to assist as an instructor for BBST Foundations.  I am also brushing up on  Gojko Adzic’s Specification by Example and Impact Mapping.  I drafted this post as I flew home to Florida from new job orientation in California.  That is big news.  I wear a product owner hat now.  I will remained focused on quality in software delivery in an agile environment for a different organization. I get to apply the testing mindset upfront in processes in direct collaboration with customers and as part of the development team!

Although, I have been a wallflower in the software testing community since last August – not actively participating in professional online groups – in the last year I did manage to contribute 3 company DevBlog entries and to do a few talks, which I now have listed in a Speaking page on this site.  Thanks for reaching out to me Matt Heusser and thank you for creating interactive spaces like TestRetreat and Software Delivery 24/7 for quality-minded folks to support each other and to learn from one another.

*Oh yeah, in closing, from back in the day, here is one of my favorite tracks from the aforementioned namesake album.   I hope you enjoy this tune, Rain King.