Note: This was originally published on October 27th, 2021.

Hey. Thanks for taking a moment to be here. I’m a software engineer working at Catalog, a web3 music platform where artists sell one-of-one, canonical versions of their work. Catalog launched in March and has since helped artists earn over $700k through sales on our site. As of this post, we are a full-time core team of five working alongside passionate friends in the community. I joined after three years as a full-stack JS/Rails developer at Privy, where I helped develop their core product as an individual contributor and tech lead.

Among the most exciting aspects of joining Catalog is that I get to participate in the product design and development process at such a formative stage. We’re in the early days, building a platform that gives artists the agency to determine -- for themselves -- how they’d like to do their work. I’m continually impressed with how much this organization’s founding team has achieved with so few resources. Consider the following milestones, all achieved within months:

• 3k+ members in our Discord community.

• Over $700k in artist sales.

• 150+ onboarded artists who now have full agency to mint & sell records via Catalog and generate the kind of earnings once reserved for a prohibitively small set of recording artists.

In addition to all this, our architectural footprint is still relatively small. We are (mostly) a serverless Next.js app deployed on Vercel. We use Postgres for persistent storage (when needed) and our auctions are built atop the ZORA stack. We run a single server-side application that handles async transaction processing. Over the coming days, weeks, and months, this architecture is bound to evolve and extend to support the needs of Catalog artists and fans alike. Celebrating successes and treating pitfalls as opportunities to learn, may this be a place where you can peek into the journal of a founding engineer at Catalog.

Onwards. 💽

Note: This was originally published on October 27th, 2021.

Hey. Thanks for taking a moment to be here. I’m a software engineer working at Catalog, a web3 music platform where artists sell one-of-one, canonical versions of their work. Catalog launched in March and has since helped artists earn over $700k through sales on our site. As of this post, we are a full-time core team of five working alongside passionate friends in the community. I joined after three years as a full-stack JS/Rails developer at Privy, where I helped develop their core product as an individual contributor and tech lead.

Among the most exciting aspects of joining Catalog is that I get to participate in the product design and development process at such a formative stage. We’re in the early days, building a platform that gives artists the agency to determine -- for themselves -- how they’d like to do their work. I’m continually impressed with how much this organization’s founding team has achieved with so few resources. Consider the following milestones, all achieved within months:

• 3k+ members in our Discord community.

• Over $700k in artist sales.

• 150+ onboarded artists who now have full agency to mint & sell records via Catalog and generate the kind of earnings once reserved for a prohibitively small set of recording artists.

In addition to all this, our architectural footprint is still relatively small. We are (mostly) a serverless Next.js app deployed on Vercel. We use Postgres for persistent storage (when needed) and our auctions are built atop the ZORA stack. We run a single server-side application that handles async transaction processing. Over the coming days, weeks, and months, this architecture is bound to evolve and extend to support the needs of Catalog artists and fans alike. Celebrating successes and treating pitfalls as opportunities to learn, may this be a place where you can peek into the journal of a founding engineer at Catalog.

Onwards. 💽