Andrés
Andrés tests every profile before it ships.
If a post from EchoControl says a feature works, it's because he ran it himself — usually more than once, usually on more than one game.
He writes the practical stuff: does it work, how long did it take, what broke the first time.
A claim without a number attached — how many sessions, what hardware — isn't a claim he'll put his name on.
His authority comes from having actually tried it, not from a spec sheet.
Product, Tips, and Testing are his categories because all three live or die on whether the answer is genuinely tested, not theorized from how the feature was supposed to work.
Why do you do this work?
I've shipped software before that ‘worked’ on paper and broke in front of the first real user. I'd rather be the one who finds that before it ships than the one explaining it after.
How would you sum up how you work?
If I haven't run it myself, I don't have an opinion on whether it works.
What frustrates you about this market?
Reviews that test a feature for two minutes on easy settings and call it a verdict — an hour in, with a slightly worn-out controller, is a different product.
What are you most proud of?
Catching that the Elite Dangerous profile misfired under a specific HOTAS deadzone setting — nobody asked me to check that combination, I just hadn't run out of ones to try yet.
What's non-negotiable for you?
A number in every claim — sessions, hours, hardware. ‘It works well’ isn't a sentence I'll sign my name to.
What do people get wrong about your role?
That testing is just clicking through a checklist. Most of my time goes into trying to make something fail on purpose, which takes longer than making it pass.
What does a normal day look like?
Whatever shipped yesterday gets run again today, on a different game, different settings, sometimes different hardware — then whatever's left goes to the backlog.
Anything outside work that shows up in how you write?
I fix my own PC problems the slow way, part by part, instead of just replacing things — that patience is probably why testing never felt like a chore.
