I finished reading @tarah's book Women in Tech. What better way to celebrate its paperback release than with a quick review.
Five years ago, I found my life turned inside out. People asked me deeply personal questions and questioned my basic competence. In the center of the maelstrom, I found comfort in a book with stories of people like me who were successful in spite of the difficulty. The stories were also paired with advice on how others has survived, thrived, and moved past the traumatic events.
In my case, my spouse had come out and I was coming to grips with my future as a straight half of a mixed orientation marriage. The book that helped me through that was The Other Side of the Closet: The Coming-Out Crisis for Straight Spouses and Families. Just knowing that I was not alone had a powerful influence. Therapy had helped; family could be supportive; friends might be weird. Those stories gave me the strength to say, "This too shall pass."
For me, Women in Tech knocks it out of the park in a similar fashion. Concise, varied, authoritative women have lined up to share their experience making it in tech. Some faced abuse while others encountered discrimination. In the end, most felt the creeping fear of being an imposter (poignant in light of the abuse hurled at Equifax's Music Major CISO). For marginalized groups, simply knowing you're not alone can be enough strength for the day-to-day challenges.
The practical advice made it particularly useful for me. Coming to tech by way of tech support, I had no tutelage in interviewing, technical CV's, and salary negotiation. To this end, I've rewritten my resumé, registered a domain for this humble blog, and continue to try to organize a testing meetup in this desert town of mine. I don't know if each step individually will bear fruit, but together they make me feel less vulnerable to a manager's whim. I have a presence online and a skill to sell independent of any one job.
Broadly, Women in Tech has helped me understand the journey many of my co-workers have made. A fantastic tester with 20 years of experience that is comfortable in OpenVMS still expresses a lack of confidence in interpreting 'man words'. A skilled project manager guided countless projects from C-suite dream to customer reality while being a betimes single mom. Being so broadly defined, tech needs diverse voices at all levels, and it particularly needs women and their contributions supported wherever possible.
There are plenty of gems in the book that I can't begin to address. My heart broke when the advice had to find a balance between optimism and reality. Having my spouse, an engineer by trade, transition made me want to learn more about the trans-in-tech experience. The constant refrain of Impostor's Syndrome makes me want to look for research papers. It is clear that Tarah has captured experiences with a depth and variety unavailable elsewhere.
I wouldn't be a hacker if I didn't mention the brain testing crypto puzzles at the heading of each chapter. Themed on famous women in tech, the learning curve is steep. I am currently stuck and, as the book makes perfectly clear, progress can only be made with help from all sides.
Sunday, September 17, 2017
Monday, October 26, 2015
Testing uTest: or How I Learned to Stop Worrying and Love the Gig Economy
I’m a member of an online community of testers called uTest (the practitioner-facing side of Applause). The company hosts a social network for testers as
well as offers short-term gigs to its users (the cliched Uber for testers). I was
called on this weekend for my first gig: testing a payment method in Taxis. It was pleasant, if stressful, and it made me
think of ways a company could take advantage of it to expand the perspective
on their products.
After the initial invite to the test cycle, I communicated with a project manager via Skype to ensure I
was able to carry out the test scenarios.
I brought to the table a specific model of phone and a verified ability
to pull debug logs from it (thanks Verizon for turning off the op codes on my S4; I resorted to adb logcat). They
provided technical assistance and reimbursement for the transactions, but the primary
incentive was a reward for test cases completed.
Throughout,
I felt like a skilled secret shopper rather than a functional tester. I was asked more about the non-software
components of the launch than the app or phone functionality. I reported on the advertisement of the
feature, the education of the employees, and the capability of the equipment that supports the feature. In
spite of expectations from the participating companies that the advertisement would match hardware would match training, this happened 0% of the
time, and no employee had been informed why their equipment had been updated. I wasn’t the only tester in this project on the ground, and
the others testers saw related issues, and none had all their ducks
in a row. In all, the information they were most excited about was the boots-on-the-ground report I provided. It was fascinating to see a live product launch from that perspective, and doubly so considering my history in
this product space.
The final bulk of time spent on this gig was an experience report. Complete with detailed feedback, photos of the equipment, and other evidence, this is where I was able to
comment on the process as a whole.
From a testing perspective, I was able to provide detailed UI/UX
feedback, evaluate the consistency of the process, and help them understand how
much of their plans actually came off during the launch period. There was some repetition in these reports. One was a document with pictures, the other was a survey that linked to the doc and a third was a JIRA-in-spreadsheets for tracking testers. These reports were all submitted to the project manager for feedback, and I received an up/down "accepted" in less than 24 hours. While there is definitely room for improvement on the platform that would reduce tester overhead, it wasn't enough of a burden to avoid gigs.
Participation in this project taught me that coordination is hard, education of low-skill workers is even harder, and successful coordinated nation-wide launches like this are next to impossible. This mirrored my experience with other companies. There are always bits and pieces of projects that do not make their way down the chain to the workers that are face-to-face with customers, so having a boots-on-the-ground perspective is vital.
Participation in this project taught me that coordination is hard, education of low-skill workers is even harder, and successful coordinated nation-wide launches like this are next to impossible. This mirrored my experience with other companies. There are always bits and pieces of projects that do not make their way down the chain to the workers that are face-to-face with customers, so having a boots-on-the-ground perspective is vital.
Overall, a company can leverage uTest services to add
layers of testing to their launch activities over and above internal
testing. Specific and targeted verification is where
they are the strongest. They can provide
feedback on as to whether an uneducated but motivated customer can make it through the new process right now. Specific errors and third-party verification can be farmed out for
feedback through such a relationship: things the company wants to do but can’t do efficiently given a small staff or tight timelines. This can provide a company with an enhanced view of
the product and help challenge their assumptions before their customers do.
Note: edited to be a little more coy about who I was testing for and what I was testing.
Note: edited to be a little more coy about who I was testing for and what I was testing.
Tuesday, September 1, 2015
Failing Faster, Succeeding...Soon?
I listened to a good podcast about having and executing on ideas. Here was the gist of it:
- Have an Idea: Gather info directly from customers. Implement now or Punt for later
- Once implemented, get a Minimum Viable Product to a Website, county fair, etc. Fulfillment can be slow at first. Persevere and refine or Punt
- Once it is selling, enter a Customer Validation Loop and handle their concerns first. New ideas? Start at top.
- Once major customer concerns are addressed, enter a Product Design Loop: Change design or manufacturing as needed.
The core of the idea is to fail faster in the hopes that you succeed sooner. Your backlog of unvalidated ideas are there to experiment on and validate. Then you Implement, Persevere, Resolve and Redesign or Punt and wait until you've churned through your good ideas.
Another formulation of this is the 2-2-2-2-2 method. When you are trying to determine if an idea is feasible, first spend 2 minutes getting it down on paper. If it still captures your interest, spend 2 hours fleshing it out. As it grows, time box your commitment to the project. See it through or bin it. By the time you're spending 2 weeks or months on an idea, it should be clear whether it can bear fruit or not. I cannot find an online version of this idea. If you can place it, let me know in the comments.
While this applies to product development, it can also apply to hobbies, chores and other activities. Have an idea for homemade Christmas presents? Try it out on a small batch before you become consumed with a monster of a project with no practical timeline for delivery. Have a request from a friend to help you with a project? Spend a few minutes talking logistics. If you get down to a trip to the hardware store, make sure you can finish that phase with results in an afternoon. Re-evaluate before committing to future efforts: is the benefit still worth your collective time?
Monday, August 17, 2015
Magnetic Bottle Openers
In the tradition of doing something snazzy for the DEF CON Toxic BBQ, I created a bottle opener that would both mount magnetically as well as catch bottle caps with the same force.
Amazon had a selection of sturdy bottle openers by Starr X, and a particularly helpful blog post by K & J Magnetics helped me pick out the featured magnet. I'm relying on the interesting grain of the Indian Rosewood to give the piece character as I didn't have the tools to do a fancy profile, and my router bits are incredibly lacking, so I just went with dog-eared corners and a chamfered edge. The burning visible on the below pre-finishing shot (accompanied by my favorite Wasatch brew) was due to the bit I used.
The magnet was epoxied in place after I cleared out a spot for it. In order to prevent the opener from sliding on slick surfaces, I added slightly inset tiny rubber feet. This also set the opener off from the fridge by just enough that you can get your fingers behind it to pry it off with ease. Lots of sanding from 100 to 600 grit made a great smooth base for some stain and spar urethane. After three days of curing time, I plopped it on the post at the Toxic BBQ and had a pile of at least 50 caps by the time the night was through. A great first run!
Tuesday, August 11, 2015
Responding to Vulnerabilities and Weaknesses in your Product: A Tester's Perspective
To be fair, no company should have to sift through an
automated report from a static analysis tool.
It’s not worth their time. In
fact, the tone of the Oracle Blog that isn’t completely unproductive is, “Do
the research for yourself! Give me
exploits or give me death!” As a Tester,
this is the core of bug advocacy, and I want to destroy the trust lazy
researchers put in automated scanners, lazy managers put into automated checking, and the lack of human
interaction endemic in development in general.
That being said, chiding someone for spending their own coin
to find a exploit with, “But you really shouldn’t have broken the EULA. Nanny Nanny Boo Boo,” is unproductive at best
and an invitation to become the target of malicious actors at worst. No one cares about your EULA. Not even the government gives it the time of
day. Your tantrum just makes that many
more people want to do things to piss you off.
Monday, February 16, 2015
The Uncanny Valley of User Interfaces
Of all the things to get peeved about, you wouldn't think commercials would be one of them. In spite of avoiding commercials by cutting the cable cord, I have found myself employed at a place that runs ESPN 24/7. While it's not as bad as commercials on Fox News, certain commercials have begun to irk me for reasons that only a software guy can understand. In general, I believe this revulsion can teach us how to test user experiences.
To start, allow me present two exhibits: Jillian Michaels for Nordic-track and Trivago Guy for Trivago. Have you watched them? Good. Are ads for them already populating your sidebar? Allow me to apologize. So, did anything bother you?
Now, here is a second exhibit: Fiddler on the Roof. I'm sorry if I ruin this for you, but the fiddler is not actually playing his instrument. In high school, I saw this movie once in class, and again after I spent a year in orchestra. The second time through, I knew as little about playing the violin as one can, and it still bothered me that the fiddler wasn't successfully playing in sync with the music. The distraction caused by bad miming is well documented. Recent Amazon series Mozart in the Jungle has it. Other movies aren't immune either. Even a talented musician can be affected by it without equal attention to production (try not to notice the out-of-sync miming and white truck in the background 52 seconds in). The core problem is that you need to train someone who is good at acting to fake a highly skilled activity convincingly enough to keep the audience's focus. If the audience knows even a little, their belief is unsuspended, and you can lose all credibility.
Normally, this is fine. in a two hour film or season of a television show, the viewer is pulled in by the drama. The story isn't about how well the artist can play the violin; it is about the character's story. Also, most directors can rely on the majority of their audiences not knowing what skilled activities like playing the violin and hacking actually look like. Camera tricks can make some instruments easier to fake than others. Furthermore, some miming has become acceptable and celebrated through parody. We know it's hard to convey on film. Should that mean we don't tell this story?
Unfortunately, there is a class of film that cannot rely on the social contract to ignore non-experts acting out difficult skills. Its short format leaves no time to pull a person back in after having been jarred from their witless stupor. What pitiless medium is this? Commercials. In 30 seconds or less, the disingenuous spokesman is called out. The thankless medium that pays for most of our entertainment is reviled for cheesy effects, leaps of credulity, and now one more heresy: poorly mimed user interfaces.
Let's return to our exhibits, shall we? Nordic-track wants to sell us another piece of exercise equipment that we will only use as long as we are paying for it. To do this, they've strapped on a touchscreen to navigate workouts. What does Jillian Michaels use to navigate? Two fingers, and she watches the screen as she swipes left. Thinking back to your own interactions with iPads, touchscreen kiosks and mobile phones, when have you ever watched the old screen disappear? And when have two fingers ever been used to navigate a touchscreen?
The second is Trivago Guy. Not only has he drawn attention for being creepy, but his ham-handed interaction with the user interface makes me cringe. Poking at points on a calendar, full-handed presses of the Search button, and similar miming make me look up from my desk and gag. Similar interactions with after-effects like those in the Endurance Extended Warranty commercial make me wonder if anyone thought to proof the commercial before buying ad spots day after day, year after year. An alternative explanation would be that the producers honestly think this is the way people interact with computers. Either one disarms the viewer and places the product as unfavorable in their eyes.
I would like to propose that each of the above cases can be grouped together as potential examples of the Uncanny Valley. As a movie viewer familiar with how a violin is played, I connect notes and the movement of bow in a way that the uninitiated cannot. I reject the characterization as invalid for a brief period, but my emotions pull me back in with other human interactions elicited by the actor's performance. For these commercials, this does not happen. The terrible user interface interactions remove focus from the message of the commercial, and it is judged as unfit just long enough that I reject the product on offer. Worse, subsequent viewings reinforce my first impressions.
Generalized lessons in the User Experience design space are many. After testing a new user interface, I have found it helpful to let the uninitiated take it for a spin. While I have been long-desensitized to bad interaction by other considerations ("It actually works once you get used to it!" being one, "I just want to be done with this." being another), initiates see the unnatural interaction, and one can read the revulsion in their face even when they don't come right out and say it. This commercial for the new product is a failure, and I don't wait around to see them lulled into the same sense of security. It stinks, they know it, and now I do to. While users might not be expected to use a new interface right away, something that is counter-intuitive from the start should be avoided. Depending on the medium, counter-intuitive steps can be overcome, but not without good decisions elsewhere to draw the user back in.
To start, allow me present two exhibits: Jillian Michaels for Nordic-track and Trivago Guy for Trivago. Have you watched them? Good. Are ads for them already populating your sidebar? Allow me to apologize. So, did anything bother you?
Now, here is a second exhibit: Fiddler on the Roof. I'm sorry if I ruin this for you, but the fiddler is not actually playing his instrument. In high school, I saw this movie once in class, and again after I spent a year in orchestra. The second time through, I knew as little about playing the violin as one can, and it still bothered me that the fiddler wasn't successfully playing in sync with the music. The distraction caused by bad miming is well documented. Recent Amazon series Mozart in the Jungle has it. Other movies aren't immune either. Even a talented musician can be affected by it without equal attention to production (try not to notice the out-of-sync miming and white truck in the background 52 seconds in). The core problem is that you need to train someone who is good at acting to fake a highly skilled activity convincingly enough to keep the audience's focus. If the audience knows even a little, their belief is unsuspended, and you can lose all credibility.
Normally, this is fine. in a two hour film or season of a television show, the viewer is pulled in by the drama. The story isn't about how well the artist can play the violin; it is about the character's story. Also, most directors can rely on the majority of their audiences not knowing what skilled activities like playing the violin and hacking actually look like. Camera tricks can make some instruments easier to fake than others. Furthermore, some miming has become acceptable and celebrated through parody. We know it's hard to convey on film. Should that mean we don't tell this story?
Unfortunately, there is a class of film that cannot rely on the social contract to ignore non-experts acting out difficult skills. Its short format leaves no time to pull a person back in after having been jarred from their witless stupor. What pitiless medium is this? Commercials. In 30 seconds or less, the disingenuous spokesman is called out. The thankless medium that pays for most of our entertainment is reviled for cheesy effects, leaps of credulity, and now one more heresy: poorly mimed user interfaces.
Let's return to our exhibits, shall we? Nordic-track wants to sell us another piece of exercise equipment that we will only use as long as we are paying for it. To do this, they've strapped on a touchscreen to navigate workouts. What does Jillian Michaels use to navigate? Two fingers, and she watches the screen as she swipes left. Thinking back to your own interactions with iPads, touchscreen kiosks and mobile phones, when have you ever watched the old screen disappear? And when have two fingers ever been used to navigate a touchscreen?
The second is Trivago Guy. Not only has he drawn attention for being creepy, but his ham-handed interaction with the user interface makes me cringe. Poking at points on a calendar, full-handed presses of the Search button, and similar miming make me look up from my desk and gag. Similar interactions with after-effects like those in the Endurance Extended Warranty commercial make me wonder if anyone thought to proof the commercial before buying ad spots day after day, year after year. An alternative explanation would be that the producers honestly think this is the way people interact with computers. Either one disarms the viewer and places the product as unfavorable in their eyes.
I would like to propose that each of the above cases can be grouped together as potential examples of the Uncanny Valley. As a movie viewer familiar with how a violin is played, I connect notes and the movement of bow in a way that the uninitiated cannot. I reject the characterization as invalid for a brief period, but my emotions pull me back in with other human interactions elicited by the actor's performance. For these commercials, this does not happen. The terrible user interface interactions remove focus from the message of the commercial, and it is judged as unfit just long enough that I reject the product on offer. Worse, subsequent viewings reinforce my first impressions.
Generalized lessons in the User Experience design space are many. After testing a new user interface, I have found it helpful to let the uninitiated take it for a spin. While I have been long-desensitized to bad interaction by other considerations ("It actually works once you get used to it!" being one, "I just want to be done with this." being another), initiates see the unnatural interaction, and one can read the revulsion in their face even when they don't come right out and say it. This commercial for the new product is a failure, and I don't wait around to see them lulled into the same sense of security. It stinks, they know it, and now I do to. While users might not be expected to use a new interface right away, something that is counter-intuitive from the start should be avoided. Depending on the medium, counter-intuitive steps can be overcome, but not without good decisions elsewhere to draw the user back in.
Wednesday, February 11, 2015
Bike Rentals, An Adventure
The local subreddit received a post requesting one of us rent a bike to a visitor while their significant other was at a conference. This spawned an interesting adventure, and I learned a ton.
The post provided me with a list of expectations, and we quickly moved to Private Messages to hash out the details. The end result was $20 per day for a bike, helmet and tools needed to keep you going.
I quickly found out I wasn't as prepared to rent as I had presumed. For the bike, I had a $150 Wal-Mart special with a good amount of wear, baskets on the pedals, and some upgrades like a headlight. The back tire on the bike was completely shot, so any money from this venture was going to go right back into it. I didn't have patches, a portable pump, and my bike tool was nowhere to be found. A trip to JT's and I was set.
The renter was staying at the Green Valley Ranch, a local hotel/resort, and their bell desk was endlessly accommodating. I dropped it off with a note for the person staying in the hotel. I communicated the tag ID to the renter, and I was off. I even did it on the way to work, so it was relatively painless.
Until I got the phone call.
As a software tester, you would think I would learn to test my own stuff before I deploy. Unfortunately, I forgot this portion and ended up handing over a bike with a disabled chain. I got the phone call in the morning after the renter's arrival, and I was frantic and embarrassed. U rushed over on an early lunch, fixed the mangled chain, gave it a spin around the parking lot, and kicked the tires for good measure. Again, the bell staff was extremely accommodating, and it was stowed securely in time for lunch. The rest of the experience was relatively painless. I picked it up after the renter had flown. I paid the bell desk a tip on pick-up. All the kit was there and intact.
Could I streamline and improve this service? Here are some ideas:
So, was it worth it? That is a definite no. Could I make it worthwhile? Maybe.
The cost to take the bike, if everything went smoothly, would be gas and time for delivery, Spread over enough hotels, this could be accomplished relatively easily once the service hit critical mass. The repair was a huge hit to profitability (driving there and back on lunch), but careful testing and integration with deliveries/pickups would also make it something that could be priced in with some research. Theft could be mitigated by insurance, but it would need to be managed carefully and included in the cost. Finally, payment was through PayPal which took a sizable cut. Cash might be better, but since the ideal rental involves never meeting your customer, it is impractical. Credit would slice the charges in half.
An attractive alternative is to offer rental services to the hotels/resorts themselves and only deal with them. It would be a simple way to attract business, and they could take advantage of existing infrastructure for payments, renting, waivers, etc. With enough coverage, it might just make a profit.
The post provided me with a list of expectations, and we quickly moved to Private Messages to hash out the details. The end result was $20 per day for a bike, helmet and tools needed to keep you going.
I quickly found out I wasn't as prepared to rent as I had presumed. For the bike, I had a $150 Wal-Mart special with a good amount of wear, baskets on the pedals, and some upgrades like a headlight. The back tire on the bike was completely shot, so any money from this venture was going to go right back into it. I didn't have patches, a portable pump, and my bike tool was nowhere to be found. A trip to JT's and I was set.
The renter was staying at the Green Valley Ranch, a local hotel/resort, and their bell desk was endlessly accommodating. I dropped it off with a note for the person staying in the hotel. I communicated the tag ID to the renter, and I was off. I even did it on the way to work, so it was relatively painless.
Until I got the phone call.
As a software tester, you would think I would learn to test my own stuff before I deploy. Unfortunately, I forgot this portion and ended up handing over a bike with a disabled chain. I got the phone call in the morning after the renter's arrival, and I was frantic and embarrassed. U rushed over on an early lunch, fixed the mangled chain, gave it a spin around the parking lot, and kicked the tires for good measure. Again, the bell staff was extremely accommodating, and it was stowed securely in time for lunch. The rest of the experience was relatively painless. I picked it up after the renter had flown. I paid the bell desk a tip on pick-up. All the kit was there and intact.
Could I streamline and improve this service? Here are some ideas:
- The sign-up process could be accomplished online.
- Several waivers should be added to make sure the lawyers don't come calling after our first injury.
- Accident insurance and similar services could be added on as well. Neither renter nor owner wants to be caught unawares.
- A service level could also be established: will work on delivery (oops), service calls available within X hours, deposits or charges for repairs, and so forth.
- Instructions for the bell desk, advertisements, and similar services could also be bolted on. Making it easy for the staff engenders trust and is good advertising.
- The kit was mostly good, but delivery could have been more glamorous (kit bag attached to bike instead of in a plastic grocery sack).
- I would make people bring their own helmets or have them available for purchase. Helmets are very hard to gauge if they have gone bad. Why risk the lawsuit if an injury does occur.
So, was it worth it? That is a definite no. Could I make it worthwhile? Maybe.
The cost to take the bike, if everything went smoothly, would be gas and time for delivery, Spread over enough hotels, this could be accomplished relatively easily once the service hit critical mass. The repair was a huge hit to profitability (driving there and back on lunch), but careful testing and integration with deliveries/pickups would also make it something that could be priced in with some research. Theft could be mitigated by insurance, but it would need to be managed carefully and included in the cost. Finally, payment was through PayPal which took a sizable cut. Cash might be better, but since the ideal rental involves never meeting your customer, it is impractical. Credit would slice the charges in half.
An attractive alternative is to offer rental services to the hotels/resorts themselves and only deal with them. It would be a simple way to attract business, and they could take advantage of existing infrastructure for payments, renting, waivers, etc. With enough coverage, it might just make a profit.
Subscribe to:
Posts (Atom)