“Quality is never an accident; it is always the result of intelligent effort.” - John Ruskin
If you’ve followed my journey, from dropping out of a sports college to accidentally building a career in QA, you might think this is about work.
It’s not. Not entirely.
This is about what happens when you spend years thinking about edge cases, failure modes, and how things break. It changes you. Not just as a professional, but as a person.
QA Is a Mindset, Not a Job Title
Most people think quality assurance means “find bugs.” And sure, that’s part of it. But the real skill is something deeper:
Thinking about what could go wrong before it goes wrong.
At Commenda, I don’t just test features after they’re built. I sit in design reviews and ask uncomfortable questions. I challenge assumptions in sprint planning. I think about what happens when a user does the one thing nobody expected them to do.
That’s not testing. That’s thinking ahead. And once you develop that muscle, you can’t turn it off.
“Everybody has a plan until they get punched in the mouth.” - Mike Tyson
Software doesn’t follow your happy path. Neither does life.
Edge Cases Are Real Life
In QA, we obsess over edge cases: the unusual inputs, the unexpected sequences, the one-in-a-thousand scenarios that somehow happen on day one of production.
Here’s what I’ve realized: life is mostly edge cases.
- The career path that makes no sense on paper but works perfectly in practice
- The decision you made under pressure that turned out to be the best one
- The person you met by accident who changed your trajectory
None of these follow the “happy path.” They’re all edge cases. And the people who handle them well are the ones who’ve trained themselves to expect the unexpected.
QA gave me that training.
The Shift-Left Philosophy
There’s a concept in modern QA called “shifting left”, which is about catching problems earlier in the process rather than waiting until the end. Instead of testing after development, you integrate quality into every stage: design, planning, development, and deployment.
At Commenda, we built GitHub CI/CD pipelines that run automated regression tests on every pull request. We used AI tools like Cursor and Stably.ai to generate test scenarios. We reduced customer First Response Time from 5 hours to under 5 minutes, not by adding more people, but by building better systems.
But here’s the life lesson in shift-left:
Don’t wait for things to break before you start caring about quality.
In your career, that means investing in skills before you need them. In relationships, it means having hard conversations early. In life, it means building systems and habits that prevent problems rather than reacting to them.
“The best time to plant a tree was 20 years ago. The second best time is now.”
Ownership Changes Everything
The biggest shift in my career happened when I stopped thinking of myself as “the person who finds bugs” and started thinking of myself as “the person who owns quality.”
Those are very different things.
Finding bugs is reactive. Owning quality is proactive. It means:
- Caring about the user experience before anyone files a ticket
- Building monitoring dashboards because you want to know when things go wrong, not because someone asked you to
- Taking responsibility for customer success, not just feature stability
- Understanding the business (compliance, operations, workflows) because quality doesn’t exist in a vacuum
At Cedcoss, I learned to see products from the business side. At Commenda, I learned to own the entire quality lifecycle. The combination made me something I didn’t expect to become: someone who cares about the whole picture, not just their piece of it.
Product Empathy
The most underrated skill in tech isn’t coding or testing or project management.
It’s empathy.
Understanding what the user actually needs. Feeling the friction they feel. Knowing that the “minor bug” you’re about to deprioritize is the thing that makes someone’s day worse.
QA taught me this because testing is fundamentally an act of empathy. You’re putting yourself in the user’s shoes, all the users, including the ones who use your product in ways you never imagined.
The Do-or-Die Mindset
I’ve written about this in my earlier posts, but it bears repeating: the mindset I built as a kid chasing sports dreams is the same mindset that drives me in QA.
- Discipline: Testing is repetitive. You do it anyway, every single time.
- Resilience: You find a critical bug at 6pm on a Friday. You deal with it.
- Competitiveness: Not against others, but against mediocrity. Against “good enough.”
- Finishing what you start: If I pick up a feature to test, I test it completely. No shortcuts.
“Limits and fears are nothing but illusions.” - Michael Jordan
What I Know Now
Three companies, three completely different roles, and one thread running through all of it: show up, pay attention, and never stop learning.
QA taught me to think ahead. Business analysis taught me to see the big picture. Product operations taught me to own the outcome.
But more than any of that, this journey taught me that the path doesn’t have to be straight to be right.
I didn’t plan any of this. I just kept moving forward, kept saying yes to hard things, and kept holding myself to a standard that felt uncomfortable.
And honestly? I wouldn’t change a single detour.
“Looking back, I didn’t plan this journey, but every step prepared me for where I am today.”
If you haven’t already, check out how it all started and the career journey.