Hey, I’m Gene.

For years, I’ve been the person my family comes to when something stops working, figure out what happened and how to make it work again.

I’ve always enjoyed that part of tech too. I like learning how something works, but I enjoy it even more when I can explain it in a way that helps someone else.

You don’t need to know everything about tech to belong here.

Maybe you’re trying to figure out whether a new pair of earbuds is worth buying. Maybe your phone has a feature you know exists, but you have no idea why you’d actually use it. Maybe you already know quite a bit about tech and just want to hear someone else’s point of view.

All of that is welcome.

I want GearWyze to be a place where people can learn without being talked down to. You can know more than me, less than me, or disagree with me entirely.

The important part is being open to another perspective.

I’m still learning too. Part of the reason I enjoy doing this is that every new product gives me another excuse to understand something I didn’t know before.

Hopefully I can teach you something along the way, and hopefully you’ll teach me something new too.

I try to give products enough time before I make a final call on them. How long that takes really depends on what I’m testing.

A pair of earbuds may only need a week or two before I have a good sense of the comfort, sound, controls, battery life, or any connection issues. Something like a phone, computer, or game may need several weeks or longer.

I like giving that initial excitement some time to wear off because that’s usually when you start noticing the smaller things. Maybe the battery isn’t lasting as long the way you expected, a feature you thought you’d use all the time barely gets touched, or some weird bug keeps showing up.

I’d rather give a product the time it needs than rush out a review that is mostly a spec sheet with a verdict attached.

Reviews are about helping you decide

My goal isn’t to convince everyone to agree with me.

I want you to understand why I reached my conclusion.

A review should help you decide whether something makes sense for your life, your budget, and the way you use your tech.

Sometimes my conclusion will line up perfectly with yours. Sometimes it won’t.

Either way, I hope you come away with enough information to make up your own mind, even if you end up seeing the product differently than I do.ew.

Sometimes a company might send me something to review. If they do, I’ll tell you.

Getting a product for free doesn’t mean I owe the company a good review. If I like it, I’ll say so. If I don’t, I’ll say that too.

I’m fine with a company checking that I got the basic facts right, like a feature, price, compatibility, or spec. What they don’t get to do is rewrite my opinion or ask me to make something sound better for them.

If working with a company means I can’t be honest about the product, I’d rather not do it.

I want GearWyze to be accurate, but I know I can get something wrong. Products can change after I publish too.

If I’m fixing a typo, broken link, formatting issue, or cleaning up some wording without changing what the article says, I’ll usually just fix it.

If I get an important fact wrong, I’ll add a note explaining what changed. I’ll do the same if a software or firmware update, more testing, or new information changes something important after the article goes up.

And if any of that changes my recommendation, I’ll make that clear too.