About Screen Fix

It started with a USB-c cable that kept breaking

It was a winter evening in 2018, and I’d just unboxed a brand-new MacBook Pro. The cable that came in the box was flimsy—literally. The first time I plugged it in, the connector snapped halfway inside the port. The machine didn’t even power on.

I pulled it out, and the metal prongs inside the cable bent like taffy. The store’s replacement was identical.

I tried three more cables over the next two weeks. One melted the port’s insulation after six hours. Another’s connector split open under the slightest pressure. The last one worked for a full day before the same thing happened.

Each time, I’d call Apple support, explain the issue, and get the same response: ‘This isn’t covered under warranty.’

The problem wasn’t just the cables. It was the assumption that they’d *just work*. No one warned me that USB-C connectors were fragile, that cheap cables could fry ports, or that ‘certified’ didn’t always mean *durable*.

I spent hours researching, testing, and documenting which cables actually lasted—only to realise no one else had done that systematically.

Nine tries before it worked

The first ‘fix’ was to wrap the cable’s connector in electrical tape—a temporary bandage that failed after two charges. The second attempt involved buying a ‘premium’ cable, only to find it still bent under the weight of the laptop’s hinge.

By the fifth try, I’d disassembled a working cable to study its internal wiring, only to realise the solder joints were the weak link.

The sixth cable, a $50 ‘industrial-grade’ model, lasted a week before its insulation cracked near the port. The seventh was a custom-built one from a local electronics shop, but the connector’s plastic housing warped when I plugged it in.

It took nine attempts—including a failed DIY soldering session that nearly shorted my desk—to find a cable that held up for more than a month without failing.

The winning cable wasn’t the most expensive or the ‘official’ one. It was a mid-range Anker model with a reinforced connector and thicker internal shielding. But here’s the catch: none of the reviews online mentioned its durability. The specs were there, but the *real-world* testing wasn’t.

That’s when I realised the gap wasn’t in the hardware—it was in the *documentation* of what actually works.

The mind behind these pages

That was me—Stanley Rasmussen—staring at a bent USB-C port and a pile of broken cables. I’d spent my childhood taking apart VCRs and rewiring extension cords, but this was different. The problem wasn’t just the hardware; it was the *information* around it.

No one had written down what actually lasted, what to avoid, or how to spot a flimsy cable before it ruined your device.

I’m the kind of person who keeps trying even when it’s obvious I’m doing something wrong. My first computer was a hand-me-down 486 that ate floppy disks, and I spent more time fixing it than using it.

My grandmother used to say I had ‘a stubbornness for things that don’t work,’ which is why I ended up in tech support before I turned 20—listening to people describe problems no one had documented.

I don’t cook, I don’t garden, and I’ve never built a physical product. But I *do* know how to read a schematic, how to spot a shoddy solder joint, and how to write a troubleshooting guide that doesn’t assume you’re an engineer.

That broken cable was the last straw. If no one was writing down what *actually* works, then I would.

Everything here is written the way that cable was tested

This site doesn’t just copy and paste solutions from forums or manufacturer pages. Every tutorial, review, and troubleshooting guide starts with a real problem—like that cable—and doesn’t stop until it’s either fixed or we’ve mapped out why it’s not.

If a driver update causes issues, we test it on three different machines. If a ‘quick fix’ for a printer jam doesn’t work, we try five alternatives before publishing.

We keep notes on every attempt, even the failures. That’s why you’ll see sections like ‘What We Tried First’ or ‘Why This Didn’t Work’—because the path to the solution matters just as much as the solution itself. And if a product or method still doesn’t work after nine tries?

We say so. No false promises.

Months later, those notes become the pages you read. The cable that took nine attempts to fix became the framework for how we approach every problem: test it, break it, document what happens, and then tell you the truth—not the version that sounds good in a manual.

What that means for you

You’ll find no ‘just plug this in’ advice here. If a solution works, we’ll tell you why—and if it doesn’t, we’ll tell you that too. Every page is built on the same principle: we won’t publish anything until it’s been tested the way that cable was tested.

That means no vague instructions, no skipped steps, and no assumptions about what you already know.

What you *won’t* find are ads for the latest gadgets, sponsored ‘best of’ lists, or affiliate links disguised as reviews. This site exists because someone needed to ask: *‘How do I know this will work?’* And the answer wasn’t out there.