Wesley Harding. Available for projects
Custom websites, databases, and the systems that connect them — Los Angeles

Wesley Harding

I build systems end to end, connecting the physical to the digital — software that keeps track so you don't have to.

Prefer the code? github.com/wesleyharding3

Wesley Harding

Systems I built and run end to end — the same kind of thing I can build for your business.

WorkThree systems, in the wild
Wear the Future — wordmark

Showroom Inventory

A QR code on every garment — so the showroom always knows where each piece is, who has it, and when it's due back.

A real fashion house in Los Angeles runs its day on this. Stylists, editors, and celebrities borrow sample garments to photograph and wear; each piece has a QR code. A staffer scans it with a phone to check it out or back in, and the system records who took it, why, and when it's due back. Nothing gets lost, and anyone on the team can see the truth at a glance.

It runs several brands at once, and each one only ever sees its own pieces — kept separate by the database itself, not by hoping every line of code remembers to ask.

And it isn't just the dashboard: I'm building the showroom an app to go with it, so clients and administrators can reach the business's crucial knowledge anywhere there's internet service.

Three printed scarves from the America 250 collection on a rack
Blue and red paisley scarf
Floral folk-print headscarf

Fig. 01 — a real collection. The physical inventory the system tracks, piece by piece.

246real press placements tracked across 14 brands
3types of users — owner, brand, stylist — one app
How a scan works
01
Scan
phone scans
the tag
02
Look up
find the
exact piece
03
Out or back
who has it,
why, due date
04
Record
logged to a
permanent history
05
Update
status updated
for everyone
What made it hard

Most of the work is invisible — making sure the system stays correct even when it's busy, shared, and handling money.

i.
Keeping each brand's inventory private

Several brands share one system, and each can only ever see its own pieces. That rule lives in the database itself — so a mistake in the code can never leak one client's inventory to another.

ii.
Handling payments safely

Stylists pay a one-time fee to reserve pieces. The payment is confirmed on the server, where the amount can't be tampered with from a browser.

iii.
Proving the press was worth it

When a borrowed piece shows up in a magazine or on a red carpet, the system ties that coverage back to the exact loan — turning PR into a number a brand can actually see.

iv.
One code, two worlds

A single QR code links the physical garment to its digital record. The same code prints on the binder page and the hanger tag, so the rack and the records never drift apart.

Under the hood — for the technically minded
Next.js 15 (App Router) · Supabase / Postgres · Stripe · TypeScript · Vercel. github.com/wesleyharding3/wtf
Isolation28 row-level-security policies enforced in Postgres, with security definer helper functions (locked search_path to avoid policy recursion) and anti-escalation triggers that block a user from changing their own role, org, or billing flags. Correctness lives in the schema, where it can't be forgotten.
PaymentsStripe Checkout with the card saved on file, fulfilled by a signature-verified webhook that recomputes the amount server-side and never trusts the client.
Earned mediaA check-out's purpose links the loan to the coverage it produced; a tier-weighted, time-decayed EMV ranking turns press into an indexed ROI — never a client's raw dollars.
TaggingA single tag_id abstracted across qr / nfc / rfid; in-house QR generation, RLS-scoped so a brand can only ever mint its own codes.
Scope9 tables · 12 enums · 11 SQL functions · 3 derived views · 25 typed, validated API routes.
The companion app — just entering development

The dashboard runs the showroom from a desk. The app puts the same crucial business knowledge — where every piece is, what's due back, what the press was worth — in clients' and administrators' hands, anywhere there's internet service.

9:41●●●
Wear the Future
Today
38
pieces out
9
due this week
2
overdue — tap to send a reminder
Silk Soul — kimono No.4out · editor
BEALICE — Beatrice totedue Fri
Jendue — wrap dressreturned
9:41●●●
Piece
Paisley scarf No.12
Statusout — stylist
Due backJul 11
Last scanDTLA · 2d ago
9:41●●●
Earned media
This month
246
press placements tracked, all time
Vogue onlinetier 1
Red-carpet appearancetier 1
Stylist socialtier 3
Local editorialtier 2

Fig. 02 — mock screens from the companion app, drawn in code. The real one is in development now.

Working today

  • Scan-in / scan-out, with a permanent history of every piece
  • Separate views for the owner, each brand, and stylists
  • Payments, press-coverage value, and printable binder & hanger tags

Next on the list

  • The companion app — the whole business, from a phone
  • Automatic reminders when a piece is overdue
  • Self-serve onboarding for new stylists
earth00

Reads thousands of news stories in dozens of languages and figures out which ones are about the same event.

A side project, and a hard one. If I can untangle the world's news across 48 languages, your inventory and customer data are well within reach.

Пекин  ·  北京  ·  بكين
recognized as →
beijing

Fig. 03 — the same city, written three ways, understood as one. That's the whole trick, at scale.

What made it hard

The hard part isn't collecting the news — it's realizing that an article in Mandarin and one in Arabic are the same story, when they don't share a single word.

Under the hood — how it actually works
Node.js · PostgreSQL + pgvector · Claude Haiku · DeepL · local transformers · Three.js. github.com/wesleyharding3/earth1000
ReadScript-aware extraction across Latin, Cyrillic, Arabic, and CJK — language detected from the text itself, with CJK / Thai / Khmer segmentation. A frequency-list prefilter drops ~45% of language-model calls before they happen.
NormalizeClaude Haiku maps non-English keywords to one canonical English form; a three-layer cascade resolves entities against a ~21k local list, then Wikidata, then the model. About $1.80 a day at steady state.
GroupA local CPU model embeds every article into a 384-dimensional vector at $0 per run; nearest-neighbor search plus union-find clusters coverage into story threads, with a guard against runaway clusters.
RankBayesian classification blended with exponential recency decay (24-hour half-life) and diversity cooldowns, so a few loud sources can't dominate.
PipelineCollect → read → group → rank → show, over ~266K articles per cycle. 18 source-type handlers · 72 tables · 24 scheduled workers · a 3D globe · a daily AI audio briefing · ships as a native iOS app.
The finished thing
earth00 3D globe with country borders
earth00 story view with country labels and a source breakdown
earth00 trending-topics list

Fig. 04 — the live app: a 3D globe, a story with where its coverage came from, and the day's trending topics.

And people watch
50,000combined impressions a week — daily video briefings, auto-published across platforms
48languages read, every cycle

Two storefronts, one fashion house

The showroom's own shop — and the handbag label I designed from the ground up.

BEALICE is a high-fashion handbag brand based in Minnesota. I designed the site — the typography, the pacing, the whole feel — and built it on Shopify, so the label runs its own store without a developer on call. bealice.com is live now.

And Wear the Future — the same fashion house whose showroom runs on the inventory system above — has its public face at wear-thefuture.com: a Shopify storefront that turns the showroom's physical collections into a shoppable catalog, brand by brand.

Same discipline, different register: where the inventory system is about correctness, a storefront is about feel — type, imagery, and rhythm doing the selling. I do both ends.

bealice.com
bealice.com homepage — high-fashion handbag brand
bealice.com/collections/shop-all
bealice.com shop-all collection grid
wear-thefuture.com
wear-thefuture.com storefront homepage
wear-thefuture.com/collections/silk-soul
wear-thefuture.com Silk & Soul collection page

Fig. 05 — stills from both live stores. BEALICE designed end to end; Wear the Future's storefront built as the front of house for the showroom system.

ServicesWhat I can build for you
i.
A website that looks right and works

A fast, clean site that represents your business properly and does exactly what you need — not a template a thousand other places already use.

ii.
A database to organize and make sense of your stuff

One reliable home for your inventory, customers, orders, or records — so you can actually find things, trust the numbers, and see what's going on.

iii.
The link between the two and your real-world operations

The connection that reaches into what you physically run — scanning inventory, tracking who has what, automating the busywork that eats your day.

How working together works
01
You tell me the problem
in plain words — what's slow, lost, or driving you crazy
02
I scope it
a clear plan and a fixed quote, before any work starts
03
I build it
you see progress along the way, not just at the end
04
You own it
it's yours — the code, the data, all of it

Every project starts with a free conversation and a clear, fixed quote — you'll know what it costs before anything begins.

AboutHow I work

A report that's wrong loses money the same night.

Before I wrote software, I spent eight-plus years running restaurant and entertainment operations across Los Angeles, Portland, and San Diego — hands-on with the spreadsheets, schedules, and numbers that kept the doors open. That's where I learned to respect real-world systems: a report that's wrong costs you that same night.

So I build the way I'd want a system built for my own business. I'd rather the software itself prevent mistakes than count on everyone to remember the rules. And when something breaks, I find the real cause and fix that — instead of rebuilding from scratch.

AWS Cloud Practitioner certified · CompTIA Data+ · finishing a B.S. in Data Science at WGU.

The tools I useFor the technically minded
PostgreSQL
Schema design, row-level security, PL/pgSQL functions & triggers, pgvector, materialized views, purpose-built indexing.
TypeScript / Node
Next.js App Router (server components, route handlers, middleware), typed database layers, and Express services.
NLP & data
Multilingual keyword extraction, entity resolution, local transformer embeddings on pgvector, and Python ETL.
Front-end
Hand-written CSS design systems (no UI kit), responsive layouts, and Three.js data visualization.
Payments & auth
Stripe Checkout + signature-verified webhooks, and secure sign-in (magic-link / invite / password).
Hosting & infrastructure
Vercel & Render, cloud storage, security-header hardening, iOS packaging. AWS Cloud Practitioner.
Beyond the code
Music production
Composition, sound design, and mixing in Ableton Live.
3D & animation
Blender — modeling, animation, and rendered motion graphics.
Video & content strategy
Editing and automated publishing pipelines — earth00's daily video briefings earn a combined ~50,000 impressions a week.
ContactGet in touch

Let's build something that works.

Tell me what your business needs and I'll tell you how I'd build it. No jargon, no obligation — just a straight answer.