The Instant-Reject List: 5 Rules for Better Code Reviews
Drowning in pull requests? An Instant-Reject List sets 5 agreed-upon rules so teams can reject low-quality PRs quickly and keep code review sane.
Helping teams ship their code confidently, from development to testing to deployment.
Drowning in pull requests? An Instant-Reject List sets 5 agreed-upon rules so teams can reject low-quality PRs quickly and keep code review sane.
AI-assisted coding broke the feedback loop that builds engineering judgment. Here's how junior engineers can rebuild it on their own terms.
Test suites rarely get slow overnight. They decay gradually until no one remembers when the build turned into a 20-minute wait.
JUnit XML is everywhere in CI, but there's no official spec. Here's why every tool generates different output and what to parse from them.
Heroku announced they're moving to a 'sustaining engineering model.' Here's what it really means and how to plan your next move.
After 20+ years as a developer, AI tools felt like a threat. Here's how I went from hating them to using them in my daily work.
Slow CI builds cost more than time. They kill focus, erode trust, and quietly drag down your entire team. Here's what's really at stake.
What separates good test automation from the bad? It depends on your project, but these are a few that show you're on the right track.
Every decision in software development and testing means sacrificing something, and most don't realize what they're giving up.
Stop waiting for GitHub Actions. Rails 8.1's local CI runs your tests in seconds on your own machine. Here's how it works.
When you spend time up front thinking about your approach before diving into code, you'll end up with a much better result.
Stop letting developers dismiss your bug reports by saying it works for them when you know something's broken.
Things are changing on the Dev Tester website. Check out what's coming down the road.
Do you fix bugs before adding new features? If you do, you're probably making it more difficult to maintain your apps in the long run.
For testers joining an existing team that has never established any quality guidelines, how can you begin to make a difference?