We caught up with the brilliant and insightful Ryan Craven a few weeks ago and have shared our conversation below.

Ryan, appreciate you joining us today. What do you think it takes to be successful?

I recognize that quality engineers and content creators require both unique skills tailored to their crafts and shared attributes like passion and diligence that drive excellence across different pursuits.

Quality Engineer Perspective:
• Strong technical skills – Must have expertise in testing methodologies, writing automation scripts, using testing tools, and understanding how software systems work. Staying up-to-date on the latest technologies is important.
• Attention to detail – Testing requires meticulously going through requirements, identifying edge cases, and documenting defects. Strong analytical and problem solving skills are key.
• Communication – Need to clearly communicate defects and test results to developers and stakeholders. Collaboration is essential.
• Process oriented – Following established processes and standards for testing is critical. Methodical approach and well documented tests.

Content Creator Perspective:
• Creativity – Ability to come up with engaging ideas and translate them into content that resonates with your audience. Think outside the box.
• Consistency – Produce content on a regular schedule and maintain quality over time. Commitment is key.
• Understanding your audience – Know who you are creating for and what motivates them. Tailor content accordingly. Interactive with your community.
• Marketing/Promotion – Getting your content seen requires promotion, networking, social media savvy. Entrepreneurial spirit helps.

Similarities:
• Diligence – Careful and persistent work effort is required for success in both fields. Perseverance through challenges.
• Passion – Genuine interest and enthusiasm for your work drives motivation and excellence.
• Continuous learning – Need to continually expand your skills and knowledge. Adaptability is important as industries evolve.
• Attention to metrics – Key metrics like test coverage or viewership numbers should be analyzed and optimized. Quantifiable measures of success.

I recognized a unique opportunity to promote the importance of software quality while satisfying my passion for teaching others. This led me to create a YouTube channel focused on software testing techniques and strategies, as well as blogs on Medium and Substack.
When I first started my career as a quality engineer, I noticed there was a lack of engaging resources that could make topics like test automation accessible for a wide audience. I believed that testing is a critical phase in delivering robust software products that users can trust.
So I decided to fill this gap by launching ryancraventech – a channel where I break down testing concepts through tutorials, case studies and lively discussions. My goal was to showcase this often overlooked discipline as both an art and a science.
I also began blogging on platforms like Medium and Substack to provide in-depth written guides and commentary on the software industry. This allowed me to expand on topics that I cover in my videos.
Over time, the channel and blogs also became a platform for me to explore my fascination with emerging technologies like AI. I aim to simplify complex subjects so viewers and readers can grasp how innovations like machine learning are transforming software development.
The journey of building an audience and community around ryancraventech, Medium, and Substack has been incredibly rewarding. My anecdote illustrates how identifying a unique niche and adding value for others can lead to remarkable personal and professional growth. I’m excited to continue using online education and entertainment to advance software excellence.

Awesome – so before we get into the rest of our questions, can you briefly introduce yourself to our readers.

My journey into software testing and content creation stems from over a decade of experience in highly technical roles, where discipline and attention to detail are paramount. After serving 5 years in the Navy operating submarine weapon systems, I pursued computer engineering and worked in avionics. This instilled an appreciation of quality and standardization that I carried into software testing.

As a quality assurance engineer, I found great fulfillment in advocating for the customer and ensuring robust, reliable software. Testing is often perceived as an afterthought, so I saw an opportunity to showcase its intricacies through educational content. I began writing blogs and making videos to demystify concepts like test automation and CI/CD pipelines. Feedback showed this filled a need for digestible, engaging testing resources.

My content, published under the handle on Medium (Ryan Craven) or Substack (ryancraventech), aims to balance software theory with practical examples from my work. I leverage my engineering background to unpack complex topics and advocate for quality assurance’s vital, multifaceted role in the industry. I believe elevating technology’s practitioners spurs greater innovation. My goal is to not only teach but inspire and entertain through a unique blend of expertise and creativity. I also address philosophies on how to calibrate a healthy relationship with technology. My book ‘Tech-Life Balance’ explores this.

I manage this endeavor while working full-time, because I’m passionate about pushing quality assurance forward. I’m always open to collaborations, as combining perspectives is one of the best ways to enrich technical content creation.

What do you find most rewarding about being a creative?

The most rewarding aspect of being a content creator is undoubtedly the interactions I get to have with viewers, readers, and fellow creators. There is nothing quite like receiving a comment, message, or review from someone who connected with or learned from my work.

Knowing that I was able to teach a complex software testing technique in an accessible way, or provide a new perspective on technology’s role in our lives, is incredibly fulfilling. The whole purpose of putting my ideas out into the world is to engage with an audience. When a concept clicks for someone because of how I presented it, that’s success in my book.

Beyond just teaching, I find great value in the dialogues and relationships that blossom through my content. Connecting with fellow engineers, testers, and creators opens up new ways of thinking and collaborating. The creative process becomes far more rewarding when you have peers to share ideas with and learn from.

At the end of the day, focusing on enriching people’s understanding, perspectives, and connections through education and entertainment is what motivates me. The chance to have a positive impact on others through content makes all the effort worthwhile. There’s nothing more gratifying than knowing my work provided value to someone.

What’s a lesson you had to unlearn and what’s the backstory?

One key lesson I’ve had to unlearn is relying too heavily on commanding people rather than having an open dialogue. In the military, directives are often issued as orders without room for discussion. This ensures obedience in high-stakes situations.

However, I learned that approach can backfire in the private sector.

In software engineering teams, blunt commands tend to demotivate rather than inspire action. I had to understand that while lives aren’t on the line, people still respond better when you make requests, not demands. Each person has different communication needs.

Early in my civilian career, I would often issue direct orders out of habit from the military. But I noticed this style sometimes made teammates uncomfortable or less eager to collaborate. I had to make a conscious effort to stop simply telling people what to do, and learn how to have more open, two-way conversations. I had to unlearn giving instructions and start focusing more on listening. This helped create an environment of engagement rather than tension with my coworkers.

The book “Turn the Ship Around!” by L. David Marquet really drove home the importance of empowering teams and giving them ownership, rather than commanding them.

Now I take the time to understand how each coworker prefers to receive information. Some need more details and justification; others want bottom-line instructions. I tailor my requests accordingly and make them two-way conversations, not one-way directives.

The military ingrained in me the mindset of issuing top-down commands. But I’ve worked hard to adopt a more collaborative, flexible leadership style that fits the situations I now work in. I had to appreciate that software teams need empowerment and dialogue, not just decrees. It continues to be an evolving process.

Contact Info:

• Instagram: https://www.instagram.com/ryancraventech/
• Facebook: https://www.facebook.com/Ryancraventech/
• Linkedin: https://www.linkedin.com/in/ryanmcraven/
• Twitter: https://x.com/ryancraven_qa
• Youtube: https://www.youtube.com/@SpareMeAI
• Other: https://www.hopp.bio/ryancraventech