Meeting Cabin's Technical Needs

TL;DR

Cabin's plan for 2024 includes a lot of technical work: app changes, citizenship minting improvements, necessary maintenance, potential whitelabel efforts, etc. Beyond this known work, we also need to stay agile and explore the space of possibilities that leads to Cabin's success. I started working on all of that when I joined the First Fellowship five months ago. Now that the fellowship is over, I'm submitting a proposal to continue to fund that work.

Team

• Sponsor: @grin
• Steward: @grin

Goals

The proposal includes three goals:

1. Complete Roadmapped Work
2. Map Out and Complete Future Work
3. Maintain Cabin's Lead

Complete Roadmapped Work

The winter roadmap has the following technical goals:

• 1. Make Citizenship Better a. Develop City Directory b. Improve new Citizen experience
• 2. Grow active Citizens a. Reduce friction to become a Citizen
• 3. Improve data and analytics a. Migrate DB to SQL b. Create dashboards

Doing this work well requires a deep understanding of web2 and web3 development, as well Cabin's specific needs. After working at the First Fellowship, I'm very familiar with Cabin's tech stack and have a clear idea of how to accomplish all these goals. In fact I've already started working on 3a since it is urgent.

Map Out and Complete Future Work

Executing on the winter roadmap above is the first step, but there's much more to do. I made several suggestions in my network state conf debrief, and I have others, like this:

The right approach will require paying attention to what users want and sequencing the work for maximum effect. I will work closely with Jon, other contributors, our citizens, and the wider Cabin community to understand what needs to be done, then do it.

Maintain Cabin's Lead

Beyond shipping code, Cabin must successfully map out the idea maze between where we are now and the network city we want to create. While technical work will be the bulk of this proposal, I plan to spend some time strategizing with Jon, exploring new possibilities, connecting with others in the space, doing thought-leadery things (writing, podcasting, posting on Farcaster), and generally repping Cabin (as I did in Amsterdam). This has benefits in both directions: it helps us understand how we want to achieve our goals, and it helps others find us and collaborate with us.

Why Me

This proposal is a big ask. Why should Cabin trust me to do all this? First, because I was the First Fellowship tech lead for the last five months, so I'm very familiar with the tech and the team (and they with me). Second, I have lots of relevant experience. Before joining Cabin, I founded two successful companies and designed and built multiple widely-used products. I've also created adjacent projects such Vibecamp and FarCon, and have been interested in this space for several years now.

Proposed Budget

1 year of funding for this work:

• $200,000 USDC
• 2400 ₡ABIN

This is a 20% reduction from my pay at the First Fellowship.

Timeline and Deliverables

Timeline: 1 year, at which point the proposal can be reviewed and renewed as needed

Deliverables: Cabin meets it's present and future technical needs