Tech.
Recommended Guide + Tech Reviews. What to buy, what to skip, and why — in plain English. No sponsored picks. Scores are ours.
Recommended Guide.
Start here if you don't want to read 40 reviews. One pick per category, one runner-up, one to skip.
Best Laptop for Most People
Pick: 14" Air-style laptop, 16GB / 512GB
Light, fast, battery all day. Don't pay for the Pro unless you edit video daily.
Runner-up: 15" version if you want bigger screen.
Skip: 8GB in 2026. You will regret it in 6 months.
Best Phone
Pick: Main flagship, base storage
Camera + 5 years updates > 1TB storage you won't use.
Runner-up: Last year's flagship, refurbished.
Skip: Ultra / Max / Pro Max unless you actually zoom that far.
Best Headphones
Pick: Noise-cancelling over-ears, $250-350 range
ANC + comfort > brand name. Try them on if you can.
Runner-up: Good earbuds if you hate headbands.
Skip: “Gaming” headsets for music. They are for mic, not music.
Best Budget Setup Under $600
Pick: Refurb laptop + decent monitor + $50 keyboard/mouse
Monitor matters more than RGB.
Runner-up: Used desktop + new SSD.
Skip: Brand-new cheapest laptop. It is slow on day one.
Tech Reviews.
Hands-on-ish reviews. Score = performance + value + would-we-buy-it-again. Filter by category, sort by stars.
5 = Buy it, no notes. 4 = Buy it, small flaws. 3 = Fine, wait for sale. 2 = Only if you need it now. 1 = Skip. We do not take sponsored scores.
⬇ Backend — Tech Backend — Template
Right now Tech is local-only — guides + reviews live in a hardcoded tech=[...] array in JS, filtering / sorting is in-browser, and “Full review” / “Compare” are alert() placeholders. This backend is the map to make it real: reviews + guides live on the server, the browser just filters / sorts / displays them. Proposed, not connected.
01 / Files to create
api/tech/reviews.php GET /api/tech/reviews?cat=&sort=&q= api/tech/guides.php GET /api/tech/guides api/tech/review.php GET /api/tech/review?id=... api/tech/admin-save.php POST /api/tech/admin-save (admin only) sql/tech_tables.sql
Keep the tinyfiles PHP pattern: each endpoint loads /api/bootstrap.php, uses json_in() / json_out(), prepared PDO statements.
02 / Database tables
-- sql/tech_tables.sql
tech_guides
id VARCHAR(40) PRIMARY KEY -- e.g. 'laptops', 'phones'
category VARCHAR(40) NOT NULL
title VARCHAR(120) NOT NULL
pick TEXT NOT NULL -- "14 inch Air-style laptop, 16GB / 512GB"
runner_up TEXT NOT NULL
skip TEXT NOT NULL
body TEXT NOT NULL
updated_at DATETIME NOT NULL
tech_reviews
id VARCHAR(40) PRIMARY KEY
name VARCHAR(120) NOT NULL -- "14 inch Air Laptop"
cat ENUM('Phones','Laptops','Audio','Gaming','Software') NOT NULL
price INT NOT NULL -- 1199, 0 = free
stars DECIMAL(2,1) NOT NULL -- 4.8
verdict VARCHAR(60) NOT NULL -- "Buy it" / "Fine, wait for sale"
pros TEXT NOT NULL
cons TEXT NOT NULL
by VARCHAR(60) NOT NULL -- "@tiny_tech"
desc TEXT NOT NULL
created_at DATETIME NOT NULL
updated_at DATETIME NOT NULL
One row per guide / review. No sponsored flag needed — this page says no sponsored picks, so never add a sponsored-score column.
03 / API endpoints & request flow
GET /api/tech/reviews?cat=all&sort=starsDesc&q=
- cat in [all, Phones, Laptops, Audio, Gaming, Software]
- sort in [starsDesc, priceAsc, priceDesc]
- q = search in name + desc, LIKE %q%, cap 100 chars
- returns { "ok": true, "reviews": [ { id, name, cat, price,
stars, verdict, pros, cons, by, desc }, ... ] }
GET /api/tech/guides
- returns { "ok": true, "guides": [ { id, category, title,
pick, runner_up, skip, body }, ... ] }
GET /api/tech/review?id=...
- returns one review + full body for the "Full review" page
- if id not found: { "ok": false, "error": "not-found" }
POST /api/tech/admin-save (admin only, session check)
{ "type": "review", "id": "...", "name": "...", ... }
- validates stars 0-5, price >= 0, cat in allow-list
- INSERT ... ON DUPLICATE KEY UPDATE
Filtering / sorting moves to the server so the browser never needs the full list to render a filtered view.
04 / Scores & validation (server owns this)
// Score legend on this page is the contract: // 5 = Buy it, no notes. 4 = Buy it, small flaws. // 3 = Fine, wait for sale. 2 = Only if you need it now. 1 = Skip. // We do not take sponsored scores. // Server validates on save: // stars must be 1.0-5.0, one decimal, price >= 0 // verdict must be in allow-list, cat must be in allow-list // pros / cons / desc length caps, e.g. desc <= 1000 chars // name unique, no duplicate reviews
Keep the score rule in one place — the server — so the front-end legend and the saved score can never drift apart.
05 / Frontend wiring
// Replace the hardcoded let tech=[...] in this page:
async function loadTech(){
const res = await fetch('/api/tech/reviews?cat=' + curCat +
'&sort=' + curSort + '&q=' + encodeURIComponent(q));
const data = await res.json();
// data.reviews -> same renderTech() card HTML as now
}
// Replace setCat() / setSort():
// just set curCat / curSort and call loadTech() —
// no more filtering the local array
// Replace the "Full review" alert:
// window.location = '/tech-review.html?id=' + t.id
// which calls GET /api/tech/review?id=...
// On load: GET /api/tech/guides -> render .tech-grid
// If API fails, fall back to current hardcoded tech[] array.
Keep the local array playable with no backend — if /api/tech/reviews fails, use the current in-page tech[].
api/tech/ + sql/tech_tables.sql — no GitHub needed. The <pre> blocks are the backend spec: server-owned reviews + guides, server-filtered lists, no sponsored scores.