Stefan Steinbauer
We all know what it is like to fill out a form only to find that it stalls upon hitting "submit". These glitches may be a minor annoyance to us, the everyday consumer, but to the business in question, those minor errors can compound into huge financial losses.
For the everyday consumer, software underwrites more of our daily lives than we ever realize. We interact with software a thousand times a day in a thousand tiny ways - from the obvious like checking our emails and smart phones to depositing a check and shopping for groceries.
For the everyday consumer, realizing how much software touches our daily lives is akin to waking up in the Matrix. The long list of complex operations we take for granted has only grown as society has become accustomed to having a smart phone in hand at all times.
For those of us (i.e: me) who find terms like 'scrum master' and 'agile testing' to be a little mysterious, the idea of software testing can be a bit hard to grasp. Sure, it makes sense that you need to check over your software before releasing it to the public, but after that, testing is done, right?
All branches of the government and public sector rely on software to manage and analyze the massive amounts of data they collect on a daily basis. With each department managing thousands to millions of people's data and individual needs, it is no surprise that a public sector institution requires a robust software system.
For the everyday consumer, realizing how much software touches our daily lives is akin to waking up in the Matrix. The long list of complex operations we take for granted has only grown as society has become accustomed to having a smart phone in hand at all times.
