Testing AI features, Playwright craft, and what actually gets people hired. Roughly one a week.
Why the word exists, how it decays from a label into a budget line, and why development is growing its own version of the same misnomer right now.
Fifteen things, weighted by how much each one costs you in the room. Evidence, judgement, craft, and the resume question nobody asks out loud.
Before judging whether the output is good, check whether it is the right shape. A schema assertion catches the failure that actually breaks things — and it runs in milliseconds.
A test that fails sometimes is the most honest thing in your suite. The routine I run instead of reaching for a sleep, and why "I added a wait" and "I found the collision" look identical in a diff.
What I got wrong about the gap between manual testing and automation, and what the gap actually was.
The same question, answered two ways. Same tools on the resume, very different engineers in the room.