Case study · Event discovery

Texas Heavy

A discovery platform that connects heavy music fans with concerts, festivals, bands, venues, galleries, and classifieds across Texas.

Role
Product engineer and owner
Focus
Events, ingestion, search, community
Stack
Elixir, Phoenix, PostgreSQL
Status
Independent product · Active
Texas Heavy homepage showing concert and festival discovery
The problem

Local scenes are active, but their information is fragmented.

Show announcements live on venue calendars, flyers, ticketing sites, and social posts. Fans miss events, bands and venues are represented inconsistently, and duplicate listings make a calendar less trustworthy.

The product

Build the scene around connected data.

Texas Heavy treats an event as part of a larger network of bands, venues, cities, media, and community activity.

  • Browse upcoming concerts and festivals across Texas cities.
  • Connect event lineups to reusable band and venue profiles.
  • Normalize dates, locations, source links, and event identity during ingestion.
  • Search and filter without flattening useful genre or location context.
  • Extend discovery with galleries and community classifieds.
  • Give administrators tools to review, correct, and enrich imported data.
The reliability problem

A useful calendar has to resist duplicates and stale data.

Event sources describe the same show differently. URLs change, lineup order varies, and dates can be reformatted. I built normalization and upsert behavior around canonical source identity, then added review paths for ambiguous records.

The goal is not maximum ingestion volume; it is a calendar people can trust enough to make plans from.

Engineering ownership

Domain modeling made the frontend possible.

I owned the event, band, venue, city, gallery, and classified models; ingestion and deduplication; admin workflows; search and discovery pages; deployment; and visual product design. This project demonstrates the data and operational work behind an interface that should feel simple.

Back to the beginning

Papereg

See how PDFs, scans, photos, and handwriting become structured forms and reviewable records.

Read the case study