profile

Filip Hric

To be, or not to be... (technical)

Published about 1 year ago • 1 min read

Filip Hric

13th May 2025

TO BE OR NOT TO BE (TECHNICAL)

Hey Reader!
There’s an ongoing debate in the QA world on whether it makes sense to get technical or not. I remember having a fairly heated debate on this last November at Agile Testing Days in Potsdam. My talk titled "Test like a developer, develop like a tester" argued that we should put the effort as testers to become experts in the software we test. And yes, that includes having a fair bit of developer knowledge.

Jason Arbon called this a "debate of our ancestors" and made some excellent arguments on why the more important question is asking whether you are adding value to the team or wasting everyone’s time. I agree a lot with his take. After all the real question is whether we are learning as testers, or comfortably sitting in the QA chair while industry keeps on moving and leaving us behind. If you are reading this newsletter, chances are you’re part of the first group ❤️

Blogposts, discussions, events

​Testing email flows with Mailosaur​

A short giude on how to test e2e flows that require an email to be opened. Code demonstration using Mailosaur.

​Read more →​

​Webinar: Ensuring Uptime with Playwright​

Join me and Checkly for a webinar next week, where me an Nica will show you how to write smarter Playwright tests and extend them beyond QA to production monitoring and automation.

​Read more →​

​Vibe-coding tools showdown - which one is the best?​

Few weeks ago, Jonathan Canales and I tested out different "vibe-coding tools" and scored them on different scales. Here’s a summary of our findings and a link to the livestream

​Read more →​

​99 Cypress.io tips course​

Level up your Cypress skills with bite-sized, practical tips that you can immediately apply to your testing workflow.

Filip Hric

Teaching testers about development, and developers about testing

filip@filiphric.sk, Senec, Slovakia 90301
​Unsubscribe · Preferences​

Filip Hric

I teach testers about development and developers about testing

Sign up for weekly tips on testing, development, and everything related. Unsubscribe anytime you feel like you had enough 😊

Read more from Filip Hric

Hey Reader,, A few years ago Cursor was a nicer place to type code. This week it announced Origin, its own Git competitor built for agent workloads, and got acquired by SpaceX for sixty billion dollars. Somewhere in between, it stopped being an editor and started becoming the whole stack — the place you write, review, merge, and increasingly test your software. I come from QA, so my first instinct isn’t excitement, it’s a question: when one tool owns every step of the loop, who’s the...

4 days ago • 3 min read

“Too dangerous to release” has become its own genre of AI announcement. Project Glasswing is the latest entry: not quite a product launch, but a claim about a threshold, dressed up with enough corporate coalition to signal this one is serious. Anthropic says their new security-focused model, Claude Mythos Preview, can find software vulnerabilities better than all but the most skilled human experts. George Hotz challenged the “too dangerous to release” narrative by pointing at the obvious:...

2 months ago • 2 min read

Anthropic had a rough week. And the part that stings isn’t just that something went wrong - it’s how they handled it. A map file, a DMCA frenzy, and a Python loophole On March 31st, Anthropic accidentally shipped Claude Code’s TypeScript source code via a map file left in their npm package. The leak was spotted almost immediately, and GitHub repositories mirroring the code started receiving DMCA takedowns shortly after. What followed was a fairly aggressive takedown campaign by Anthropic. One...

2 months ago • 2 min read