@edatweets_ Spending time with users of the future software. Even better: do with them the work to be improved by the software. Extremely motivating in my experience.
I don't think regulation can stop #web3, but it can certainly delay it a lot. As a community, we'd better create a self-regulating culture, so that regulators aren't tempted to "overregulate"
Imagine if uber was co-owned by drivers and riders
Now imagine if there was an "uber" service for ecosystem service markets, that was co owned and operated by:
👩🌾land stewards
🥼scientists
💸credit buyers
🌍earth herself
...
@regen_network
“The future is so complex and ultimately unpredictable that there is always the possibility of things turning out far better than we fear.” – Rebecca Solnit
So true and so good.
Despite all our accomplishments, we owe our existence to a six-inch layer of topsoil and the fact it rains.
https://t.co/rNpjiiZgdv
I just committed my first end-to-end, state altering, #cosmjs powered, communication between a #react web app and a self made #cosmos blockchain (via #ignitecli. Obviously still a lot to learn, but definitely feels good. https://t.co/3urGJaoQNo
Since 2017, we've been building together - code, community, frameworks, business relationships, and complimentary endeavors.
This month, we start shipping products that start to tie all of this together and unlock a whole new wave of building. Together.🫱🏾🫲🏼
Anyone managed to #E2E test #browserextension like @Metamask or @keplrwallet ? I mean, interacting with the popped up window triggered by JS client code. Kind of possible by launching a new tab with the extension, but pretty useless in a "wallet connect" scenario.
Remember what happened when @RegenNetworkDev shipped v 0.45 of the @cosmossdk with the authZ module and all of a sudden you could auto restake rewards?
The 0.46 release https://t.co/fjWDA5BrTY
Is going to revolutionize the cosmos ecosystem gov UX
Here is how: /Thread
So many scammers 😵💫
Anyone reading this DON'T contact a Gmail address that pretends to be Metamask official support (seems obvious, but bette safe than sorry)
@bitfield Seems to be exactly what I'm looking for. Though my research till now found that going "mockless" has heavy implication on how code is designed (pleeeenty of interfaces, for example). I gave my email so that I am notified upon release of the book :-)
I find #unittesting in #golang rather tedious, particularly #mocking, which tells me I probably lack some know-how. Anyone has a link an insightful article or doc ?