My goals today were to:
- Set up a dev blog, which we will use to further our efforts to work "in public"
- Write the first blog post for the dev blog, detailing our first month and the launch of our MVP
- RFC a new way to store Entries in our API backend (which solved a few of the outstanding issues from the MVP launch)
- Kick off the technical introduction with Zora about future integrations
I also had in mind the goal to be more communicative with the team about when I'm online and available for discussions (given that we're all remote, Slack is basically the only forum at which to reach me). I implemented a small change in Slack to make this more formal, creating a whereabouts channel that I can use to be more explicit about when I'm away or particularly focused and not available for discussion.
All of my goals were achieved, although they could have been much more efficient — especially the meetings. Both of my meetings today took two hours, which indicates that formal goals and parameters we not laid out. The net effect of this meant that I ended working at around 12 AM. In future, we should set specific goals for meetings, and know when we've reached success or failed within a time-boxed frame (unless we're just jammin').
I feel some urgency to get the Entry RFC implemented and merged soon, although it only serves to make our tech more robust, and doesn't necessarily move us forwards as a product. Therefore, implementation might need to be held off until later. This makes me uneasy, but it's fair. Instead, I will prioritize a brief personal audit of our security so far, and then attempt to dive into protocol work.
The 2-hour discussion with Zora about an integration with their new protocol implementation was fun, and I'm excited about what we can do. Immediately follow that, we had an internal meeting about our "working in public" blog strategy, and then how we might bring protocol and other web3 integrations into blog entries directly.
The idea of integrating web3 content directly into entries is super exciting, and I believe it will be a core feature of Mirror. Ecosystem-enabled, modular structures/blocks that have web3 functionality.
Even more exciting will be the opportunity to bring the community into the development of these features. If Notion has "templates" that users can buy on Gumroad, Mirror could have block-formats that people can buy on Uniswap. This requires a lot more thought, of course, but it's an interesting thread.
At the same time as we think through this, there is a strong internal desire at Mirror to have a great writing experience, and we need to be realistic about what we can ship in the near-term that's exciting and effective for our early writers. Both the time constraints and desire for world-class writing UX will likely sway us away from being too ambitious with our scope, and instead I can see us trying to work within existing standards (e.g. markdown), to hack together a prototype. The prototype will allow us to get more feedback and information, from which vantage point we can tackle the larger goal. This seems like a reasonable approach.
I didn't get to more Mirror Protocol design work, but hopefully I can start that in earnest tomorrow, and have some validated new ideas by the end of the week.