No Channel Channel.

Native

@derek what’s the timeline for /nativefun and an ETA for something to do with all this?

Web3 Product Strategy 101:

This pretty much sums it up. Web3 is marked by over promise/under deliver - wasting time and money. 

I asked was when we’d see some developments. 
The answer was essentially “you’ll get it when you get it so shut up and like it”

Web3 Product Strategy 101:

This pretty much sums it up. Web3 is marked by over promise/under deliver - wasting time and money. 

I asked was when we’d see some developments. 
The answer was essentially “you’ll get it when you get it so shut up and like it” https://warpcast.com/jayce/0xb307de22

These are my principles. If you don't like them, well, I have others

Seems pretty common for most devs. You can set a date, and on that date you can release what’s ready, but hard to predict what will be ready on a date. But also depends a bit on the kind of work that needs to be done (complex or not.) New things harder to predict.

Moderate-to-severe symptoms.


Writing a book /mirror-loom : https://paragraph.xyz/@mirrorandloom/

Didn’t strike me as ego, just awareness of what software development is like, which is not like building a bridge. Far more iterative, finding a path.

Also this is soft behavior. 

Devs, like everyone else, need skin in the game and not to have such fragile egos. 

Set a realistic date, try to hit it.. if you fail, take accountability and own it.

I mean if it is just an idea and one needs more than a year to figure out how to make it work, maybe they aren’t ready for investments.