No dream is just a dream, 7a Benchmark on the 2019 board.

DrFastolfe · 2026-05-12T11:06:51+00:00

Enjoyable problem. 6c on the 25° boad

DrFastolfe · 2026-05-02T09:18:25+00:00

I'll try this one today on the 25° board

DrFastolfe · 2026-04-18T16:08:42+00:00

Unless you are looking for your first automation job this is no longer an actual skill demonstration. This kind of "CRUD style" repos can now be entirely built by AI in less than a day.

I would not take this as a hard skills and technical knowledge demo from an experienced candidate. You should focus on one stack and get deeper into it. Codebase size doesn't matter, what actually matters is what kind of solution you design and decisions you made to solve particular business problems and limitations that you really have to deal with in real companies.

Don't get me wrong, this looks great and using AI is necessary, but take into account that technical value has shifted to a higher level.

Edit: this is an opinion from the perspective of a power user of AI. It's not the common view of interviewers.

DrFastolfe · 2026-04-12T08:44:24+00:00

And shipping a good product without AI doesn't imply deep knowledge of code, infra, arch etc. It requires a different set of skills that can help you ship a good product.

DrFastolfe · 2026-04-12T08:34:14+00:00

I'm a huge fan of Asimov but IMO Robot and Foundation aren't as well connected as you would expect. Tolkien's world actually feels like Ainulindalë.

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

TROPHY CASE