context around immutable contract implementations #2
Conversation
|
The thoughts here are good. It feels out of place here though IMO. I think "mechanism applications", or whatever you'd call this kind of brief on how the mechanism could be used, should be somewhere else. This could be a separate document, or GitHub discussion, or GitHub wiki? I like the idea of a space for that kind of stuff FWIW, thoughts about use cases, design patterns, etc. In that same vein, I think the info from the pitch should go up somewhere. There should be an overview of HoneyPause (our pitch) in text form, because nobody is going to look at the slides from Devfolio, or find our pitch on the live stream. I feel like readers will be regular people who want to know what it is/why HoneyPause won, or technical people who want to know how it works. We should def put all the info and thoughts we collected out there. I think this repo should just be the src, docs, and addresses, with anything subjective (value prop, ideas, etc) elsewhere. Like this is the technical bit, maybe thoughts about using the mechanism live in a repo/wiki under your user |
No description provided.