RE: RE: Proposal: Ecosystem Operations, Bizdev and Growth Retrospective
You are viewing a single comment's thread from:

RE: Proposal: Ecosystem Operations, Bizdev and Growth Retrospective

Words
271
Reading
2 min
Listen
Play
6M

I think all of these are good questions. I'm not sure if you're asking them to me directly, or if they're just something you want the community to tackle as part of evaluations in general. My large disagreement (which may be incorrect depending on the above) is the assumption that this proposal is only being made simply to make up for my diminishing returns and wouldn't have come up if the market hadn't soured as it has. This may not be the intention of the statement, so my disagreement only stands if it is, and that still doesn't mean it isn't valid.

I basically have to decide what to do now. I would like for that to be another X years of provable hard work, at an even greater capacity than previously, but I simply can't afford to work a full time career just to pay to then work for Hive. So either I figure out how to make it possible to keep going for many more years, or else I consider what to do next and how to best balance incoming ability to keep a roof over my head and outgoing quantity/quality of work in whichever ecosystem that makes the most sense in. In this case, I think it simply isn't logical to try to create some form on annual position or salary and just check in every year to collect– the chain and the market can't bear that, nor do I think it's the right way to approach a huge variable scope of shifting and non-numerically denominated work versus something more traditionally deliverable like a code chunk, dapp, etc.

@crimsonclad: I think all of | Ecency