Dev Tester | Improve Your Development, QA, and DevOps Skills

Like most software engineers nowadays, I have AI coding agents handling the bulk of my work.

Every software and QA engineer knows how AI is helping us get a good chunk of our work done and how fast it can ship code out the door.

“How can I make the best use of AI while still being a junior engineer?”

It’s launch day for your app, and the engineering team is putting the finishing touches on that shiny new feature that they’ve been working on for weeks.

When working with automated tests, you may have come across an XML file format called JUnit.

If you've been in tech long enough, you've seen this pattern play out.

In the past month, my software development and testing workflow has changed rather drastically and in a way that I had never expected before.

As a developer, I've lost track of how often I've had to wait around for continuous integration in the projects I work on.

A few months ago on Reddit, I stumbled upon a thread titled "What does successful automation look like to you?

I spent last weekend doing something entirely new for me: vibe coding.

Most developers and testers have been a part of this story before: You work on your feature, commit new code, and push it to the repository.

Most software developers these days are familiar with the "GitHub Flow" way of building their applications.

"I can't find the issue, this is working on my machine."

You may have noticed that the Dev Tester blog has been on a bit of a hiatus this year, with very little new content published in the past year.

Back in the year 2000, I was in the middle of my university studies and learning about software engineering when I stumbled upon a blog post titled The Joel Test: 12 Steps to Better Code.