THE DAILY COMET

refreshed Sun 6 Sept, may be stale

NFT

Classic

2026

NFT

The shops are closed but there's a dog on the roof about to jump into a hole

2022

Museum

Untitled

Picasso Museum, Barcelona · 2026

Street

The Girl with Red Mask

Gràcia, Barcelona · 2026

Street

Untitled

l'Eixample, Barcelona · 2026

Street

Untitled

Gràcia, Barcelona · 2026

Street

Untitled

Gràcia, Barcelona · 2026

Street

Untitled

Downtown, Puerto Vallarta · 2026

8 of 44 pieces

I'm an engineer who did not pursue a CS track, though I've been itching to code all my life. It all began with Computer Camp in 5th grade (summer of 1999/2000? W98?), where USF students introduced me to the basics of HTML (between Mechwarrior LAN party sessions), quickly getting me to ship my very first index.html- "Hello World" - still on a floppy disk somewhere in my closet <3

Then, another few stints- summer before high school at Vanderbilt (C++ camp); then summer before college at Berkeley (Java????). University: just a few courses in CS- Matlab, Java, Database Design.

• Daily worldsOne painted exoplanet a day, from a real NASA catalogue.

  The Daily Comet is a static site: a stack of flat text files that one build turns into plain HTML, with no database, no accounts, no tracking, and nothing that phones home while you read. Every morning at 05:00 UTC a job picks a real exoplanet out of the NASA Exoplanet Archive, builds a deterministic prompt from its type and host star, has Gemini on Vertex AI paint the scene from a fixed reference sheet so the wolf looks the same every day, stamps the frame and labels on, and leaves the finished image plus a small manifest in cloud storage for this site to read at build time.

• Event radarA weekend loop that sweeps venues and opens a pull request.

  A Claude Code loop runs on my own laptop at the weekend, sweeps Barcelona and Madrid venues sixty days out plus twelve months of tour dates for the artists I watch, scores each room by how big the crowd is likely to be, refuses to write down any event whose ticket page it did not actually read, and opens a pull request instead of publishing itself.

• OrbitTwelve months of tour dates for the artists I watch.

  The orbit page renders that same YAML as a twelve month timeline grouped by month with dates in Spain marked, the whole watchlist underneath whether an act is touring or not, and a strip of the long lead festivals that sell out months ahead.

• GalleryArt in through one command, metadata stripped on the way.

  Art arrives from a photo album through one command that exports each original, transcodes it, resizes it, re-encodes it to WebP and strips every scrap of camera, location and timestamp metadata on the way out, leaving a small YAML sidecar I can write titles and notes into later.

• Gates and deploysFour audits and a freshness check before anything ships.

  Nothing reaches the front page until one command rebuilds the whole site and clears four audits: no image may carry EXIF, ICC, XMP or IPTC data, every watched artist and live festival must actually appear on the orbit page, the type system must hold to its three font families, and a list of words that may never be published must stay absent; GitHub Actions then builds and deploys to Vercel on every push and every hour, and once a day fetches the live page back to prove today's edition really landed.

• The harnessClaude Code, a written charter, and I merge every PR.

  The site is built with Claude Code: agents work against a written charter and one living scratchpad rather than a chat history, every change arrives as a pull request with a running preview and its test output attached, and I merge every single one of them myself.