Things I enjoy the most

SEO, marketing, and how Google picks what to show

Lately this is the thing I read about most. It started with marketing, and then I got pulled into the technical side and stayed there.

Now I read about backlinks, about twiddlers, which are small functions that change the order of the results after the main ranking is already done, and about how Google tracks what people actually click.

Nobody tells you the full system. So you make a guess, change one thing, and watch what happens. It is testing with a different job title.

Writing tests people trust

Playwright and TypeScript are my favourites. The best test suite is not the biggest one. It is the one people believe when it turns red. If the team stops trusting the tests, the tests are not doing their job.

Testing AI features

AI does not give you the same answer twice. So you cannot check for one exact answer. You have to check the rules around it instead. Does it stay inside what you told it? Does it say no when it should? Does it answer in the same format every time?

This is new for most teams. I think it will soon be part of every QA job. I have done it on real products and I enjoy it a lot.

Testing on phones, not just browsers

A lot of my work now is on iPhone and Android. Phones break in ways the web does not. Permissions, notifications, coming back from the background, small screens. The same app can even behave differently on two phones.

I automate what is worth automating with Maestro and Reflect. The rest I check by hand, on a real phone. Some problems only show up when you are holding it.

Building small tools

If I have to do a boring job twice, I try to make the computer do it. That is how the pull request tool and the ticket tool started. They save the team time every day, and I get to stop doing the boring job.

Frontend work

React and Next.js were my first job and I never really left them. It helps me every day. When I can read the code, I know where to look for the problem.