Brett Owers
← All Projects

2Dueces

Idea

May 10, 2025

The final form of Crew Queue — the music crew matchmaking concept that has persisted across three iterations (queue-cloud-functions, Queue frontend, Crew Queue v2). Domain owned, plan in mind, deployment waiting for the Potatuhs ecosystem to stabilize. The idea that will not die, currently in its most patient phase.

Purpose

2Dueces is what Crew Queue became — the same concept (match musicians into functional crews that ship real songs) with a cleaner brand. The domain is owned. The architecture is designed (see Crew Queue v2 entry). The timeline is "after Potatuhs is off the ground." Some ideas need to simmer until the conditions are right.

Stack

Domain OwnedArchitecture DesignedNot Yet Built

What I Learned

  • 2Dueces is the third brand name for the same concept: Crew Queue (functional), Queue (simple), 2Dueces (memorable). The name evolution reflects branding maturity — Crew Queue describes what it does but is forgettable. Queue is too generic and unsearchable. 2Dueces is distinctive, ownable, and has the right energy for a music platform. Naming is product design.
  • Owning the domain before building the product is a low-cost commitment signal. It means: I believe in this enough to spend $12/year keeping the name reserved. It is not enough to start building. It is enough to prevent someone else from taking it while I focus on other things.
  • The decision to wait for Potatuhs ecosystem stability before building 2Dueces is the Tenlach Arcade lesson applied to a different domain: sequence matters. 2Dueces needs a content pipeline (Potatocore YouTube for music content), a commerce layer (Potatuhs for merch), and a community (the ecosystem's audience). Building 2Dueces before those exist means another cold-start problem. Building after means launching into an existing ecosystem.
  • Three iterations across six years: queue-cloud-functions (2019, backend only), Queue (2021, frontend), Crew Queue v2 (2023, architecture redesign), and now 2Dueces (2025, final form waiting for conditions). The pattern is identical to Tenlach and Intervalition: persistent ideas iterate across years until the timing, skills, and context align.

Key Insights

  • The most patient phase of an idea is the most dangerous — patient and dead look identical from the outside. The difference is internal: a dead idea does not occupy mind real estate. A patient idea does. 2Dueces still occupies mind real estate. It is patient, not dead.
  • 2Dueces under the Potatocore division (music/media arm of Potatuhs) makes the most strategic sense. Crews formed on 2Dueces produce songs. Songs become content on Potatocore's YouTube. Content drives the Potatocore brand. The brand drives audience to 2Dueces. The flywheel only works if the pieces exist. Building Potatocore first is building the flywheel's first gear.
  • Four persistent ideas in this blog have survived multiple years and iterations: Intervalition (shipped after 3 attempts), Tenlach (in development after 6 attempts), the timer+notes concept (shipped as StartNote after 4 attempts), and the crew matchmaking concept (2Dueces, waiting after 4 iterations). The pattern is undeniable: the ideas that refuse to die are the ideas worth building. The question is never "should I build this?" — it is "when?"
#music#matchmaking#crew#Potatocore#Potatuhs#domain#persistent-idea#waiting#ecosystem#flywheel

This post was composed through a conversation between Brett Owers and Claude Code (Anthropic). The content reflects Brett's recollection of each project and the lessons drawn from it. Some details may be approximate or omitted — the purpose is to paint an honest picture of a software engineer's development over time, not to serve as a precise historical record.