I Run a 1,000-Page PHP Calendar and a Portfolio That Audits Every Change I Ship

BackerLeader ●1 ●9 ●44
calendar_today ago • schedule2 min read

Originally published at bryanhamilton.info

I run two production sites alone: a DJ tour calendar that's been live since 2015, and the portfolio you're reading about now. Same stack on both - plain PHP, vanilla JavaScript, MySQL, zero frameworks. One of them earns its keep with real users. The other gets me hired. They share one rule: every change has to prove it shipped.

Site one: The DJ Calendar

About a thousand PHP/MySQL pages tracking 99 touring artists - artist hubs, city pages, venue pages, a prediction scoreboard built on a MySQL stats trick that calls tour announcements before they happen. No CMS. No build pipeline. Shared cPanel hosting, the kind everyone says you outgrow.

Running a site that old teaches you things a tutorial never will. Feeds duplicate themselves, so my upserts are idempotent and the feed gets replayed, never trusted. Users favorite artists on three devices, so the sync has to survive offline edits and tombstones. Every artist page generates its own OG share card on the fly, because nobody shares a link without an image anymore.

And because I deploy from a laptop to shared hosting with no SSH, every server change goes up as a self-verifying PHP worker: needle guards that abort if the code doesn't match, a lint gate that auto-restores on failure, self-cleaning backups, and a commit to a public deploy log after. If the worker can't prove it worked, the change didn't ship.

Site two: a portfolio that audits itself

I rebuilt bryanhamilton.info the same way I'd build a piece of rack gear. Every static page, the deploy ledger, a receipts table with over a hundred rows - one per production change, each one marked live-verified. The site keeps its own score. When an editor tab reverted my homepage a while back, the mtimes caught it. When a fix ships, the receipts row and the deploy-log commit prove which change did it.

That receipts ledger is also the honest answer to a question every hiring manager has and nobody asks out loud: did this person actually build what the resume says? Mine says "100 changes shipped, each one verified on the live site" - and you can click every row.

What carrying both has taught me

The calendar keeps me honest about production: real users find bugs at 2am and don't file tickets. The portfolio keeps me honest about craft: if I can't explain a change as a receipt, it was probably a hack. The two feed each other - the deploy-worker pattern started as a calendar habit and became a portfolio article, then a community post, then a permanent system.

Neither site uses a framework, and that's a decision, not an accident. Twenty-plus years of PHP taught me that the framework isn't what makes a system reliable - guards are. Needles that abort on mismatch. Lint gates that restore on failure. Ledgers that remember what shipped.

Question for the comments: when someone asks you to prove you can build production systems, what do you show - a resume, a repo, or a running site? I picked "a running site that proves itself," and it's the best career decision I've made.

Want more #webdev & #devops deep dives?

Join 5,986+ developers sharing real benchmarks, code breakdowns, and projects. Free forever.

More Posts

How I Built a React Portfolio in 7 Days That Landed ₹1.2L in Freelance Work

Dharanidharan - Feb 9

Sovereign Intelligence: The Complete 25,000 Word Blueprint (Download)

Pocket Portfolio - Apr 1

I’m a Senior Dev and I’ve Forgotten How to Think Without a Prompt

Karol Modelski - Mar 19

AI Email Classifier Cost per 1,000 Messages: Real Math

floxolab - Oct 8

I escaped the dot correctly and sed still rewrote a file marked DO NOT CHANGE

BashSnippets - Oct 13
chevron_left
3k Points • 54 Badges
Rochelle Park, New Jersey, US • bryanhamilton.info
24Posts
25Comments
22Connections
Full-stack web engineer · PHP & vanilla JS · 25+ years · Founder of The DJ Calendar · Open to work

Related Jobs

View all jobs →

Commenters (This Week)

1 comment
1 comment
1 comment

Contribute meaningful comments to climb the leaderboard and earn badges!