Web3 Intro for Developers • Roy Osherove • GOTO 2022

This presentation was recorded at GOTO Amsterdam 2022. #GOTOcon #GOTOams

Roy Osherove - Author of "The Art Of Unit Testing" and "Elastic Leadership: Growing Self-Organizing Teams" @osherove

ABSTRACT
In this talk Roy Osherove will discuss some of the architecture involved in building a web3 distributed application that uses a smart contract, how they interact and how a wallet such as metamask can be involved. Lastly, we'll discuss categories of skills you can become an expert in within Web3.
This is a beginner session - you are expected to have experience in programming (but not in web3) [...]

TIMECODES
00:00 Intro
01:06 Agenda
01:51 Why?
06:40 Web3 intro
12:10 Use cases
15:37 What is a blockchain?
22:22 Smart contracts
31:49 What's different?
38:19 New skills for a Web3 world
41:05 Resources
41:32 Outro

Read the full abstract here:

RECOMMENDED BOOKS

#Web3 #SmartContract #Metamask #metamasktutorial #Web30technology #Web3Tutorial #web3otechnology #web3community #web3news #Web3Intro #Blockchain #BlockchainTechnology #Decentralized #ProofOfWork #dApp

Looking for a unique learning experience?

SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.

[somethingbeautiful]

Fantastic! I'm finally starting to understand it. Thank you.

[Braindouchedotnet]

"And lastly, Trustless. Trustless basically means that instead of having centralized actors in the middle between us and what we want to do, we have the code, the smart contracts on top of the blockchain. We can see their code, we can verify their code, and we know that they're immutable and not changeable, which means we trust those smart contracts to do whatever logic we want them to do. Instead of having a person in the middle that we have to trust, we can basically remove trust between me and a third party and have a smart contract between us that allows different interactions or collaborations."

So, "trustless" means you have to have enough confidence in your own ability to evaluate code written in stone, in a system that you do not control by design, and verify that the outcome is completely predictable, has zero bugs, and will do exactly what you expect it to do, because there is no way for you to reverse a transaction if something goes wrong.

This is impossible to do. You can have confidence in the system, sure, but you cannot prove that there are no bugs, this is a fundamentally undecidable problem. This wouldn't be such a big deal if there was a way to go back and resolve errors, but there's not. You have to be perfect 100% of the time, because imperfect transactions cannot be fixed.

So that's not ideal.

[ngck]

Great primer on Web3. But the camera panning in sync with Roy as he paces is kind of distracting.

[betterstories]

“And there were Indians everywhere, and everything was dangerous..."

If you don't reevaluate your understanding of what happened to the native, indigenous people of these lands during the times of the “wild west, " or if you want to ignore the implications of the US expanding its territory into that of other peoples in order to make a point about the lawlessness, at least think twice about how you word it.