I don’t need another game.
I need a better way to decide which ones are allowed to take the hours I actually have.
That’s the entire reason this site exists.
I’m Grant Hollowell. Thirty-six. Operations data analyst in Columbus, Ohio. Husband to Megan. Dad to Owen (8) and Lucy (5). Former QA tester who still flinches at bad frame pacing and inventory screens that treat your time like it’s free. I play when the kids are down, when the work Slack finally goes quiet, and when the weekend hasn’t already been claimed by soccer, laundry, or the grill. Most weeks that adds up to somewhere between four and eight hours. Sometimes less.
Those hours are not theoretical. They’re the only ones left after the rest of the week has already taken its cut. So when a game asks for seventy dollars and then spends the first six hours teaching me its systems through busywork, or when the endgame turns into a chore list dressed up as mastery, I don’t feel challenged. I feel robbed.
Most reviews don’t talk about that part.
They talk about ambition, about world-building, about how the combat “feels.” They give you a score and a plot summary and a sense of whether the critic had a good time with unlimited evenings. Useful if your life looks like that. Less useful if you’re trying to decide whether this particular Saturday is going to feel like progress or like homework.
I used to be the guy who finished everything. Eighteen months in a local outsourcing studio doing QA left me with a permanent allergy to friction that doesn’t earn its keep—awkward controller mappings, UI that fights you, progression that looks deep on a skill tree but bottlenecks into the same three viable options. Later, logistics work taught me something simpler: patterns matter, bottlenecks matter, and anything that looks smooth on the slide deck but breaks under real use deserves to be named.
Games are no different.
So the questions I ask now are smaller and meaner:
How long until this stops feeling like onboarding and starts feeling like play?
How much of every hour is spent fighting the interface, the performance, or the systems instead of using them?
Does the endgame respect the time it asks for, or does it just keep demanding more?
Can I pick this up for ninety minutes after the kids are asleep and walk away feeling like something happened?
Those questions don’t care about critic consensus or launch-week hype. They care about whether the game earns the hours.
That’s the filter this site runs everything through.
Worth Your Weekend posts will give you the practical buying call: buy, wait for a sale, or skip—based on time-to-fun, friction, and whether the late game still feels like play instead of obligation.
System Breakdowns will dig into the loops, the skill trees, the loot logic, and the places where “depth” is just delayed competence wearing a different hat.
Frame Rate and Friction will talk about stable performance on a grown-up budget, controller support that doesn’t feel like an afterthought, and the quiet ways bad optimization taxes the people who can least afford it.
Couch Hours is the personal side—parent-player notes, co-op with an eight-year-old, and the games that still work when your brain is already tired from a fifty-hour week.
I’m not here to tell you a game is perfect. Almost none of them are. I’m here to tell you whether it earns the hours you’re actually able to give it.
A game doesn’t need to be perfect. It needs to earn the hours.
If that sentence already makes sense to you, you’re the reader this site was built for.
No notes yet — write the first.