I make clothes. The hardest question is always what to make next.
By the time a trend shows up in sales data, it is already peaking. The people who set trends talk about them years earlier, in public, for free.
Example: baggy overtook tight in Reddit fashion chatter in 2019. Today baggy holds 72% of the conversation. Most of the industry retooled years after the flip.
So I built a trend detector, and the origin story is one meetup. Data Engineers DC: DuckDB and Quack as a Postgres Replacement, moderated by 📈 William Angel and Jabari Grubb, organized by Data Community DC, Inc. , hosted at Prefect's DC office. I walked in with no experience using DuckDB.
I went home and pointed it at the 1.1 TB Reddit archive on Hugging Face. 12.1 billion items scanned in place. 67.5 million fashion comments, 158 straight months, one SQL pass, one laptop.
Now Nyce Days has a data source for which silhouettes and trends to watch. Slide 4 of the carousel is the fastest-rising cuts that are still early, led by barrel-leg jeans at x12.3.
To be clear about what this is: a signal detector for shifts in the fashion market. It will never replace taste, studying fashion history, or the tastemakers who create the shifts. My favorite collection of all time is Alexander McQueen Spring 1998, and no query will ever produce that craft or attention to detail.
Where the data earns its place: choosing pieces that will move quickly instead of mass-producing into a fading trend, and knowing which basics belong in a capsule.
If you make or buy clothing: what signal decides your next production run?
#DuckDB #DataEngineering