Sunday, October 30, 2016

Evolution Is Hard - Testing Is Evolving

"Are you ready for the next evolution?!"

- Master Chief, G.I. Jane

I think it's finally time for me to put some thoughts out there about this "Death" of QA, of the Tester role, of Testing. 

Testing is and always shall be part of everything a human does. That's simple freaking science. We test. We explore. We question. We gather information. We record data. That will never change, ever. Whether a group of people or one person does it, that question is a moot point as well. If you look at any time in history when leaps of logic, science, the arts and even industry happen, there are any number of people involved. There is always at least one. There will always be someone testing whatever there is to test however it fancies them. 

Quality and the level of how well something is done will always be a concern at some level. And depending on whether it's burritos or rockets, there's a level of tolerance which everyone agrees to. When my burrito falls apart, I'm not happy. When it's rockets carrying billions of dollars worth of payload, not to mention human lives, then having critical failures is unacceptable. We have testers in every other industry, why is software moving to eliminate this role?

Well, believe it or not, it's not being eliminated, exactly. Automation has certainly taken a huge chunk out of the need for manual testing on a regular, routine basis. I don't know anyone in the testing industry that isn't happy about that. I don't have to log in to make sure it works. Great! Now people can write scripts that makes sure login works with 500 users at the same time. Awesome! Test security threats! Test infrastructure! Excellent! Here's a bunch of tables which should work together and store a massive amount of data at the same time and the structure should be optimized to deal with several different types of user information, forms, payments, and searches. Test it! *Dies and goes to testing heaven*

Testers, the role, QA are not dying, we are evolving. We are called different things now, like Data Analysts, Performance Analyst, Security Analyst, Automation Specialist, Technical Analysts - We didn't go anywhere, we EVOLVED. 

Like the rest of the industry around us, we are quickly specializing and branching out into different things. There are still a lot of testers doing actual manual testing out there. Companies don't want to admit it, but they are using crowd-sourced testing more and more. They are taking the same money they would have put towards a department of manual testers and then using it on crowd-sourced sites, user feedback groups and even outsourcing. 

This isn't anything new. Every industry has come to this point. Companies try moving things around to make it faster and cheaper. They have to balance making the app, supporting and deploying the app and usually the last slice of the pie is for testing/customer support. 

Like customer support, jobs are being moved around to figure out where companies can still make money but people still feel like they are being supported and understood. Customer Service is a major factor and companies understand that if they cut too much or push too much to a company outside of their own, people get pissed. Yet, those same people want cheap, fast customer service included with whatever software package or device they have purchased. 

Manual testing is now in that same boat. Trust me, people are still doing this kind of testing, it's just moved out of the building and into someone's hands who isn't privy to day-to-day operations of the company itself.

Automation and testing are the gateways for junior developers. When I've had conversations with new developers, I always recommend automation positions. They know the languages, have a good set of skills to build something and companies don't really know what they want other than they think automation will fix or speed up everything. And it's true, once you reach a critical mass of certain types of automation. And folks that come out of boot camps are the most prepared to write scripts and build frameworks just to show they have what it takes to maybe, at some point, move into a developer role. 

Anyone that says testing or testers are a dying breed aren't looking hard enough. The role we used to inhabit which have served as some quality gatekeeper might be eliminated. We, as professionals might not be QA any more, we have probably become something else, or at least we are starting to. Testers, as part of the software development industry, should be good with that. We've been labeled a sub-par group in the development world long enough. We can evolve into something more. We can take our unique talents and technical skills and mind set and start carving a path and forging it instead of picking up the scraps development "tosses over a wall."

Learn about data handling. Learn to code anything. Learn to automate anything. Learn deploy. Learn to test for performance issues. Learn to test for security weaknesses. Learn to test accessibility and usability. Learn project management. Learn to specialize. Learn a little bit of everything. 

Evolution is about adaptation. Testers adapt faster than any group of people I know. We can move from one project to the next because we have basics, but we may or may not have the particulars. We learn them as we go. We use them as we need them and then move to the next thing the industry develops. While developers could be described as members of a band, testers are the jazz players, the non-conformists, the ones that look for the unique in the unexpected. We adapt. We evolve. 

So the next time someone says testing, testers or QA is dying, just tell them to wait, they haven't seen nothing yet. 

Wednesday, October 26, 2016

My November Goal: "And Now For The Rest Of The Story"

My personal goal for November is to answer a question first and then ask if the person wants more of a story or explanation of why I gave the answer I did. This is my personal goal based on feedback. I was made aware of the round about way I approach my answers, thinking I have to give an explanation up front for everything I'm going to say when a person doesn't have context.

So for you reader, you have a choice. You could leave with my stated goal, and maybe point out to me when I ramble on too much or don't get to the point. Or you can read...

"The Rest of the Story"

If you grew up in a rural area, you probably know about Paul Harvey and the "Rest of the Story." They were usually fifteen minute segments which were often played mornings and weekends on many a rural radio station. Harvey would speak to his audiences with a lilting voice and an emotional tone that came through the radio.  Sometimes the stories were funny, sad, or taught a lesson, but they always had the same format: the hook, the commercial break, and then the rest of the story.

I was first introduced to Paul Harvey working as dish washer every morning from 6 AM to 8 AM before my morning freshman Biology class. Harvey would come on about 7 AM, and then the station would go back to the upbeat rock it played that kept me slogging through all the dirty dishes tossed into the service window.

That fifteen minutes annoyed the crap out of me. It stopped my mindless drone like work and interrupted my steady beats which would keep me going in the morning. After a few months of this, I learned to keep time by the interruption. I started looking forward to the segments. I would actually stop the dishwasher or time the dishwasher noise to make sure it didn't drown out the radio.

I eventually realized what Harvey was doing with his voice and descriptions. It was a style of storytelling that drew people in, whether they wanted to be or not. You couldn't help yourself after a while. It just happened.

In college you learn the art of using the right amount of BS and actual fact to get through any number of projects. Some of them, you become completely immersed in, others you could care less about, but the story or project needed to be done to get the grade. Sometimes I would pick topics I knew well and could expand upon, others I would research late into the night and then wonder how I would make a coherent, thoughtful, organized paper of the mess of journals, books and quotes I had amassed.

Somewhere between Paul Harvey, writing college papers and eventually working in mass media, everything became a story to me. I had to be able to tell a story in 30 second bites. I had to speak witty things over the intro of songs. I had to write a compelling story about a business and how they resurfaced bathtubs. I had to create headlines that would draw the reader into the story.

Through all of that, I think my answers to questions became longer and longer and I felt compelled to tell a story, on cue if need be, to any question asked. I've even had friends remark on the fact that I would tell these long winded stories that seemed to not have a point, or would get to the point finally and it would be anti-climatic - the story was better than the point I was trying to get to. Or they were so bored with me talking, they wanted to murder me with sarcasm if it only created a point out of the words I spoke.

I didn't realize, in certain circumstances, it's very annoying. Much like I was annoyed with Paul Harvey breaking in on my musical morning, I had become the very thing that annoyed me. I had become the storyteller and mostly, I had a witty, funny things to say. Other times, I just annoyed the hell out of people.

In mass media, it's a very useful skill to be able to create something out of practically nothing. To wax poetic on lawn care and make it interesting. To find the story in the most mundane things like carpet cleaners and shoe repair.

Jump forward to my current career working in the software industry, and no one wants a story, unless they ask for it. And sometimes they do ask. They do like to hear the history behind the process or discovery because it's interesting to see where things came from.

My problem is that I assume they always want "The Rest of the Story." without the commercial break, or the hook. And maybe it's my own desire to have all of the history or all of the story that I offer that has my narrative first.

Like as an example: "Here is this workflow, which goes like this and then I decided to do this and on a whim I added this. OH and this is where I found the defect!"

OK - so it's not that bad, most of the time. Often, I've filed the defect and then everybody wants the explanation they are too busy to read, which I wrote in great detail in the defect card. So one by one, I demo the defect over and over until it's so smooth I could practically do it with my eyes closed. To the product manager, to my manager, to my developer, to my DevOps guy, to the senior architect, to other testers on the team, to content design, to whoever else gets involved with the defect. They usually don't read the defect, they run to my desk and ask for "The Rest of the Story."

I've never pushed back on this behavior because it fed into my need to tell the story, and to extrapolate and expand and explain why the defect could have gotten in there, why it might have happened, why people are interested in it, how critical it is to the product to be resolved, what I can do to help resolve it and on and on.

I realize now, it's a built in behavior I've been cultivating for a long, long time. I'm a born storyteller. When you come to me and ask a question, or tell me to show you something, I'm going to do it because I LOVE, (seriously, in all caps, to the max) LOVE, telling the story. It demonstrates value at that very moment. It lets people see what I'm seeing.

What it doesn't do is put or push the quality back into the hands of people that need to understand why something I've reported is a defect. My personal feeling on this kind of occurrence, now that I understand more about myself and this habit, is that it's removing the responsibility for understanding the problem. It enables the assumed idea that quality is always with the testing group, but it's also keeps responsibility for a defect with testing, regardless of who the defect is actually attributed to.

My Plan of Action

A) Questions in Conversations.
  • Try to answer the question first without elaboration.
  • If elaboration is requested, try to make it meaningful and succinct. 
B) Direct Questions.
  • Listen to the question.
  • Ask for clarifications.
  • Answer the question.
C) Long stories or explanations.
  • Warn people before launching into a story or explanation which might take more than 30 seconds to explain.
  • Offer the explanation but be OK with having the person turn it down or defer to later.
D) Dealing with quality issues.
  • Don't demo the bug unless absolutely necessary. Pair with person asking for the demo.
  • Expand on the explanation where necessary. Don't explain when not requested. 
  • Be mindful of long winded explanations.

E) I will try to not apologize when I do speak too long or wander down the storyteller path.

Fear not reader. I don't plan on trying to snuff out this storytelling skill. I want to shape it into something more useful, more thought provoking and more engaging when it is used. I want to get away from "Here she goes again" and move to "OH, this is interesting." I might not get there in one month. I may never hone my storyteller skill the way I want to, but knowing about a habit, good or bad, is half way to the goal already.

And That's The Rest of The Story

Tuesday, October 18, 2016

Geek Mental Health: Therapy & the Art of Learning No

“You treat a disease, you win, you lose. You treat a person, I guarantee you, you’ll win, no matter what the outcome.”

 - Robin Williams

Where to begin a story with such a heavy title is always a little daunting. I thought for a long time about publishing this in a more private space, but I feel it's necessary to do it here, where people can read and identify with my struggle and their struggles as well.

I can't say that I've been successful over the years dealing with emotional issues and relationships with coworkers. They have been some of the hardest relationships to deal with all throughout my professional career. A lot of this has to do with upbringing, schooling, and my own personal baggage about what I perceived about myself and what I perceived the other person thought about me.

Life has not been easy. I don't say that to garner sympathy. I say it simply to set my perspective. I know, rationally, others have suffered much more than I have. I know rationally that I can acknowledge that suffering, and my own and find that really, it was not the most tragic or horrific of what the world has available for experiences. But, this experience is my own, I finally understand more about how I got to this point than I ever did at any other age of my life.


There are at least two types of codependent people. The first in the constant victim state. It's the state someone lives in where everything happens to them whether it actually happened to them or not. It's a state of need that never gets filled, always feels empty and can't seem garner enough love and attention to feel valued. 

The second type is the fixer, the white knight, the people pleaser, or simply the "yes" person. I am the second type, the more passive, the less willing to say no, the gal that does it all, the one that will volunteer first no matter what is going on in my personal life. I have to fix things, rescue the fallen, swoop in and save the day. It is what I've always done best.

It's built up from a lifetime of learning a reward/response system, where in my head, cutting off my own arm is rewarding and I shouldn't complain about it, I should just do it, regardless of the damage to myself. My brain literally gets off on this kind of reward, a kind of self-harm, where my own physical and mental needs are second to someone, or to anyone else and what they need.

This can be reinforced in so many different ways, from the jobs you take, to the friendships which are formed, and even the intimate relationships you involve yourself in. These all feed into the reinforced notion that to give everything is what makes us the best, most perfect self we have. In giving we prove to everyone that we are worthy of that relationship, or job, or paycheck. Our worth is not focused on ourselves but only how much of ourselves we sacrifice for the cause, whatever that cause may be.

Mental Health & The Tech Industry

There are a lot of jobs were your mental health comes second to the job on a daily basis. Doctors, lawyers, nurses, teachers all have to deal with this in several ways. I'd like to add a large number of tech workers to this as well. The IT industry used to allow for a set pace and measured out progress. Once the computer game industry sped delivery up to a breaking point, the industry started to look for ways to develop at a much faster pace. 

This now leaves us with terms like Continuous Development and Continuous Delivery.  It's promising to a hungry tech world that there will be a constant 24/7 stream of new, shiny code just waiting for us to use, misuse, hack and then drop for the next release of bigger and better things. 

While many companies are taking a decent amount of time to get their products to market, they still release  with a lot of patches, a lot of updates which usually happen immediately after the initial download of the product. The market is flooded with mobile games which can be downloaded, played and uninstalled in a matter of minutes. 

{ If you doubt the affects the gaming industry had, watch the documentary called Atari: Game Over. The developer of the E.T. game, Howard Scott Warshaw wrote the game code in less that six weeks. The game was blamed for Atari's eventual demise. Not long after, the industry blamed Atari's downfall on E.T. and Warshaw. Warshaw later became a licensed therapist and now councils many who work in the tech industry.}

It's awesome in a lot of ways, but the downside is the cost to some of the people involved who are brilliant but become burnt out way too quickly and leave IT for other industries less demanding of their time and allow for a more creative pace. If you don't leave, there are other harbingers waiting for you, especially in the mental health department

The industry has made strides in trying to balance the work load and life, but in some corners, there is still a lot further to go. Depression and substance abuse are not the only mental health animals we should be worried about in the IT industry. The industry should also be worried about the more subtle problems, sometimes easier to hide problems many of us have like anxiety, OCD, autism, ADHD, ADD, social awkwardness, social dysfunction, eating disorders and even codependency. Many of us with these traits have figured out coping mechanisms do deal with the worse episodes. Sometimes they involve owning too many pets, other times they can involve more self destructive habits.

For me, learning skills of how to say no and protecting myself from pushing past a breaking point were not easy things. I still don't like saying no to people. I don't often think of myself first. What has been a good crutch for me are my dogs. I find it easier to tell people I can't do something because I have another responsibility. They keep the "yes" me in check at times. I can also compromise better because of them. I can say things like "I can do that, but I will need time to make sure my dogs are OK, is that OK?" Often, that small amount of time to check on them gives me the space I need to recharge, keep worries at away and do an effective job.

What my dogs can't help with is the "yes" part that pops out during meetings and in conversations where I constantly have to try to solve the problem at hand, even if I'm not the best person to do that. I blurt out the first thing in my mouth or my head. I have an extremely hard time stepping back from that instinct. I have to constantly monitor myself to make sure I'm not stepping on someone else's voice, or that I'm not just talking to talk. I empathize too much. I listen too well. I hear the pain in someone's voice and my first instinct is to offer help instead of helping them help themselves.

 It's the constant need to want to please and help people which made me a great customer service person and makes me really good tester, but sometimes it's annoying to teammates and other folks in meetings. I've learned to wait, repeat what I'm going to say in my head and if it doesn't make sense or the moment's past, then I let it go. Or I can ask for a redirect in the conversation to get back to that point if what I think is really important and I want to talk about it.

The other side of that "yes" trait is the ability to speak up and speak out. I don't stay quiet, I call out issues when I see them. I make it known when I'm not happy and when others aren't happy. I track down problems. I try to track down others who can help with those problems and work with people to get to the root and figure it out. It lets me be a very effective problem solver and someone that likes to get things done. Those are all very positive traits from codependency. I try very hard to keep those while mitigating others that are more troublesome.

The Challenge Is Ongoing

When you live with any issue, whether it's physical or mental, and you finally get fed up with what it does to you on a daily basis, you seek out help. For me, it was somatic therapy which helped to put me in a better mental balance. It helped me understand why I say "yes" to so many things and how my "no" was broken by circumstances mostly out of my control.

It taught me to recognize my emotions instead of bottling them up in a dark, safe place until the space was too full to manage and something broke. The emotion didn't matter. It could have been anything. 

It has taken several years and a lot of work to figure out what exactly I needed to understand about myself and what I need to work on which would allow me a better balance in my relationships with myself, with my work, coworkers, friends, and family.

There are moments of excitement I still blurt out things without organizing my thoughts, where I say "yes" in the moment rather than thinking my answer through. I've  gotten a lot better at catching myself when I do this. It all takes practice to re-frame your wants and needs to be center and in focus rather than keeping them barely in the picture. I still struggle with feeling selfish for the smallest things which most people don't have qualms over in the least. Hopefully I will get to the point that it doesn't seem weird to me to say "no". With any challenge, as most people know with mental health issues of any kind, you take them one day at a time.

The Tech Industry Takes Notice

If you weren't aware of it, starting on October 3rd, there was a whole week for mental health in the IT industry called Geek Mental Health Week. There are a bunch of great articles, hashtags, and events during the week to highlight mental health in the tech industry. It's the third annual Geek Mental Health Week held for the industry.

I recommend checking out the articles at Geek Mental Health, and even checking out the community and podcasts at Geek Therapy. Also check out Open Source Mental Illness online or on twitter @OSMIhelp. These are great organizations that work in the tech community to bring awareness to the struggles the industry has with mental health issues.

If you are struggling with thoughts of suicide please contact your national hotline:

                                       International List of Suicide Hotlines