I'm Varun. I make videos about hardware and games at @therevprogamers, write code that occasionally turns out to be useful, and put the long-form version of both here.
This site exists because video is a bad archive. A number mentioned in minute fourteen of a build video is effectively lost — you can't search it, skim it, copy it, or correct it later. Text fixes all four.
#What I publish
Reviews of hardware I've used long enough to have a real opinion about. Every one carries a score out of ten, an explicit what-works/what-doesn't split, and a spec table. Long-term use, not unboxing impressions.
Build guides for things I've actually done and would do again — with the reasoning attached, not just the steps.
Project write-ups for the code I publish. The repos are public; the posts cover the decisions and trade-offs rather than just the finished result.
A gear list that gets updated when my setup changes, rather than rewritten quarterly for engagement.
#The rules
- No sponsored verdicts. Sponsorships pay for videos, never for opinions. No brand sees a review before publication and no brand changes a score.
- Affiliate links are labelled. They're marked inline and disclosed at the top of any page carrying them. They cost you nothing and don't influence what makes a list — the two items I criticise hardest in my gear post have affiliate links too.
- Free hardware is declared in the post, at the top, not buried in a description.
- Corrections stay visible. When I'm wrong, the correction is dated and stays in the post rather than being quietly edited away.
- Numbers come with methodology. A benchmark without its conditions is decoration.
#How the site works
Everything you're reading is a Markdown file in a public Git repository. No CMS, no database. A build script turns the files into static HTML, and the video grid, project list and Patreon tiers pull themselves from the YouTube, GitHub and Patreon APIs on a schedule — so nothing here is a number I typed once and forgot to update.
If you want the full architecture, including the two things that didn't work, I wrote it up.
#Getting in touch
Corrections and "you're wrong about X" are genuinely welcome — the repository takes issues and pull requests, and a typo fix is a perfectly good first contribution.
If any of this has been useful, Patreon and Buy Me a Coffee are how the hardware gets paid for.