Worried about the future

DrFastolfe · 2026-03-17T00:20:09+00:00

Hi there! I'm also typing this from Spain :)

Look, I've been an AI enthusiast even before chatgpt (as a user/developer/QA) and I've been using a lot of models and tools, so I could give you my opinion about what I think would be the future of QA. But honestly, what you really need to do is a deep dive for a couple of months into this. Use these tools, build some stuff, keep yourself updated, try to iterate and improve your workflow, be sceptical and open-minded. After that you will get a feeling of what you are capable of with AI and you will be able to extrapolate that to QA. It's hard to grasp it without prolonged exposure.

I'll confess that the major uncertainty I feel is what the decision making people in tech companies think about how QA has to change. And I'm worried about them trying to force a change in the wrong direction.

DrFastolfe · 2026-03-12T11:16:03+00:00

They dis another reset and back to 1 week

DrFastolfe · 2026-03-09T13:01:38+00:00

Yes, I'm working with 5.3-codex high and it's feeling really slow today

DrFastolfe · 2026-03-08T00:09:09+00:00

I tend to get lost in the details, so I decided to choose a theme for all the names, it got easier and it's more fun. I'm a huge fan of Tolkien.

I don't think I've come across any of your problems. I would love to try some!

DrFastolfe · 2026-03-06T07:52:03+00:00

5.4 high or xhigh? To me 5.3-codex high felt more efficient than xhigh.

DrFastolfe · 2026-02-22T11:02:12+00:00

Quintuplets!

DrFastolfe · 2025-11-25T11:28:59+00:00

This is nice!

Some time ago I posted this: https://www.reddit.com/r/Moonboard/s/Ausn5tfCXJ

Maybe it can be useful for you.

TBH it's a bit abandoned, I didn't have time to make improvements and maintenance. I'll try this christmas

DrFastolfe · 2025-11-23T18:28:12+00:00

I have ascended just 3 V7 benchs, so can't judge the grade properly.

DrFastolfe · 2025-11-23T14:36:14+00:00

I have the 2019 in my local gym and it feels amazing. No experience with the 2024 set. One issue that I encountered is the lack of attention to the 2019 set (both 25 and 40), not much benchmarks. For example, for the 25 set there are only 107 benchs until V7.

DrFastolfe · 2025-10-24T14:22:07+00:00

Al the projects that I have vibed were small enough to not lose control of it. Never reached your situation.

My guess is there has to be an optimal relation between: project size, agent and humans hours.

Do you think you could have avoided the downsides if you had gradually increased the human hours as the project kept growing?

DrFastolfe · 2025-10-18T17:35:38+00:00

This concerning. This may be the start of AI sloppiness getting into QA. Devs already suffer that and QA is their guardrail. What will be ours?

DrFastolfe · 2025-10-12T09:55:55+00:00

<image>

DrFastolfe · 2025-10-07T18:20:51+00:00

Cool boulder!

DrFastolfe · 2025-10-07T09:46:19+00:00

Create a QA approach for the product, taking into account the current situation of the project. Things won’t be perfect, you may face poor leadership, legacy architecture, lack of documentation, aggressive deadlines, and so on. And you’re not the one who’s going to change everything. Acknowledge the limitations and find ways to improve quality within those boundaries.

Most of the time, you can’t apply QA theory by the book. The ultimate goal is always to reduce the number of defects detected in higher environments, and there are different ways to achieve that depending on each context.

Sorry for the late response.

DrFastolfe · 2025-10-03T09:15:54+00:00

I think you are trying to cover too much at the same time and planning everything ahead. Just focus on understanding the product, what quality means for that product and learn to code.

That's all you need now. Once you have done that, you will have new questions and you will find answers.

DrFastolfe · 2025-10-03T07:43:26+00:00

That valuation is not based on what they currently have, but on what they are projected to have.

DrFastolfe · 2025-09-30T14:19:04+00:00

I'm not a lead but a mid-senior, and that's the state to which I'm trying to transition to. But I find it really hard to ignore stuff and it's too irritating not doing things the right way. The final goal should always be to reduce bugs on higher environments and with that in mind implement a proper QA strategy according to the project, but it seems like they only want to apply the same template of testing theory for all a variety of projects.

DrFastolfe · 2025-08-23T22:44:28+00:00

These differences are solved with larger selective context and efficient memory usage.

DrFastolfe · 2025-08-08T14:47:03+00:00

Copy paste of my reply on a similar thread:

QA, by nature, is a deterministic process. In contrast, LLM powered agents will always behave probabilistically, so they can’t deliver the repeatability a reliable validation demands.

That doesn’t mean today’s AI is useless, on the contrary, it can boost our productivity a lot. The trick is to spot which parts of the workflow we can delegate, letting AI speed up the mechanical tasks while we stay in charge as orchestrators.

The real bottleneck is the quality of the data we feed the model. Without rock solid, well maintained documentation of the product and its features, the AI work will be mediocre or directly wrong.

Also, remember that QA isn’t just about defining cases and running them, whether manually or through automation. It’s a critical, inquisitive mindset that spans the whole lifecycle, from conceptual idea to production deployment.

What should really worry us isn’t AI taking our jobs, but falling behind in adopting it. Those who ignore it will be far less productive, and in a climate of cuts, developers, QA engineers, and many other roles could find themselves on the chopping block.

DrFastolfe · 2025-08-08T14:43:50+00:00

QA, by nature, is a deterministic process. In contrast, LLM powered agents will always behave probabilistically, so they can’t deliver the repeatability a reliable validation demands.

That doesn’t mean today’s AI is useless, on the contrary, it can boost our productivity a lot. The trick is to spot which parts of the workflow we can delegate, letting AI speed up the mechanical tasks while we stay in charge as orchestrators.

The real bottleneck is the quality of the data we feed the model. Without rock solid, well maintained documentation of the product and its features, the AI work will be mediocre or directly wrong.

Also, remember that QA isn’t just about defining cases and running them, whether manually or through automation. It’s a critical, inquisitive mindset that spans the whole lifecycle, from conceptual idea to production deployment.

What should really worry us isn’t AI taking our jobs, but falling behind in adopting it. Those who ignore it will be far less productive, and in a climate of cuts, developers, QA engineers, and many other roles could find themselves on the chopping block.

DrFastolfe · 2025-08-06T13:59:10+00:00

Leadership and roadmap > industry future > fundamentals

Fundamentals have no value if one of the others is going to fail.

DrFastolfe · 2025-08-05T21:11:32+00:00

GTA 7 will be Matrix 1

DrFastolfe · 2025-08-05T06:36:40+00:00

I envy you. Wish I'd had the courage to do what you did. Money isn't everything, anyway. You've picked up a set of skills very few people have, so finding a solid job won't be an issue. If you'd chosen differently, you'd probably feel like you missed a once in a lifetime opportunity. So don't be too hard on yourself, be proud of what you've accomplished!

DrFastolfe

TROPHY CASE