L1C3 - What is this NEAR Developer Certification

Captions as YouTube publishes them, usually machine-generated, so product and people names can be misheard.

1. 0:14

   okay so uh let's agree on a path what's in this week and what's not so uh we're gonna be talking about testnet localnet and betanet um and uh evm is there by the way for the person who asked about that you can use it on betanet now we're not talking about main net where it's real money real identity uh that's uh gonna be more work to figure out you know how do you operate in a defensive

2. 0:37

   environment where real capital is at stake you know how do you manage trustless contracts where you've removed all the full access keys and you want to version the contract for example some of these questions come up on mainnet where it's out of scope for this week so this week we're really talking about reading writing testing and deploying to testnet okay contract literacy not contract security if if you want to dig deep you're more

3. 1:00

   than welcome to we've got some great examples to look at but we won't be covering this explicitly nfts and fungible tokens we can talk about those but we won't talk about token economics and mechanism design we will be looking at the near core contracts but don't ask me how to port una swap to near if you gave me a week i don't know if i would even be able to give you an estimate of the level of complexity of doing that so it's it's we're keeping it simple this week and cross-contract calls how do you

4. 1:23

   communicate among contracts that's where the nearest scalability story comes in where we can get parallelization among contracts we're not going to be talking about sharded compute and storage at a theoretical level you can read the paper about that i personally have a hard time following some of those papers myself but if you get it more power to you and i would say read it and explain it to us like you're more than welcome to i would love that

5. 1:48

   so logistically we've got meetings synchronous and asynchronous activities on the left hand side monday through friday so here it's you know this time today we have a 60-minute scheduled but we can extend if we need to and then tuesday wednesday and thursday for 30 minutes we'll meet some qa logistics key questions whatever usually these meetings are lasting 30 to 60 minutes but we can continue we have two hours reserved for you everything else is asynchronous right so

6. 2:21

   uh this is the synchronous activities this welcome and the kickoff that we're doing right now tomorrow uh wednesday and thursday process and aha moments that we share and then friday we have demos uh and saying goodbye and uh asynchronous is the reading writing testing and deploying contracts it's really on you to make this week work okay a lot of self-directed work and you're gonna be working in groups by the way so you can do some solo work for sure but you'll be producing demos

7. 2:45

   as a group so what is a demo by the end of the week each team is going to deliver something that looks like this and we've got a couple of examples for you actually seven total examples so uh the scope is defined by this project nearly neighbors and don't worry about all the details here reading all these details you can check out the the repository github.com learn dashner and then nearly neighbors and basically what you'll see is this is a project like kickstarter for your neighborhood on blockchain where you can propose hey i want a

8. 3:17

   coffee shop down the street and i want to attach you know 100 near tokens to that coffee shop and that way you become one of the proposers for this project if we hit the threshold then the proposal turns into a project uh which actually realizes the coffee shop when maybe an investor and a builder come in and actually decide to make it let's say an entrepreneur and then you get you know some benefits as part of that you know uh free coffee for a year or whatever it is based on your your early investment right that's kind of the idea here so we

9. 3:47

   didn't get into all the details but it's enough to understand how do you write a contract this one is an assembly script but there are many examples in rust as well uh unit tests simulation tests the mock-ups only these are just balsamic very low fidelity you can tell very low fidelity uh wireframes and the documentation that you see splattered all over the page here including you know build commands and testing commands and so on

10. 4:11

    so there is no front end for this and again i'll remind you building a front end for this is extra it's not necessary because i i don't believe you're going to be learning very much if you're a front-end developer and you're building a front end for your contract in the end it's a few lines of code that you're using and of course there may be some patterns there in terms of how do you manage keys and access and

11. 4:34

    signing in and signing out but we have several examples about how to do this you can pick up any one of those examples and learn from it the real challenge for this week is how do you write a contract how do you write tests for that contract to avoid regression when you change how do you simulate the behavior of that contract especially multiple contracts that are communicating using cross-contract calls and how do you deploy that contract to testnet okay so focus on the back end is another

12. 5:00

    way to say that we also have three sample projects and four demo projects so the nearly neighbors is this one on the bottom left here that's highlighted in yellow but there are others so two from each two demos each from the previous two cohorts this is the third run of near certified developer you can take a look and see what they look like near riddles redirector extension near wagers near dice these are working examples and i think

13. 5:25

    the near dice and near riddles are probably the two kind of most complete examples with contracts and front end but also we have a lottery sample meme museum as a sample and nearly neighbors is a sample so this gives you an idea of of what the scope is of this work what is what is your output as a group going to look like all right groups of you know two four i would keep it maximum of four people in the group if you want to do your own individual

14. 5:56

    project that's fine as well no problem and so what does the end of this week look like defining success is that at the end of this course you can earn this l1 you know uh participant certification which says you've completed the course this week you were here you showed up you delivered a demo thank you so much for coming out the verified developer means you and i sit down or some other

15. 6:26

    experienced near developer for a 30 to 60 minute code review and and we verify that you actually understand the code that was produced you can explain it i can delete some of the code and you can come back and fix it i can change a test and you can modify the code to pass the new test for example we can refactor it we can add a new feature that's what we'll be doing in the 30 to 60 minute code review for the verified

16. 6:49

    uh developer level okay so just to give you a distinction there if you just show up participate in the demo contribute to a team um and and take shared crown for the demo that's the l1 participant if you want the verified it means you you actually need to have a code review with me or some other you know qualified reviewer where we're going to dig into the code the implementation itself

17. 7:13

    yeah and sasha i thank you has posted a little bit more about the program in the chat okay uh l2 is a future certification we have will be something like test an application with 100 users and l3 a mainnet application with a thousand users something like that to give you an idea of where we fit okay so this course here is about basic literary literacy and getting started as a remote first part-time course uh you

18. 7:38

    know where a developer can do this during their lunch hour if they have some experience in blockchain or as a junior dev you can do it maybe with like a couple of hours of work you know two to four hours of work something like that no more than six hours of work a day kind of pushing yourself okay and so what next or what else could you do at the end of this there's a during the week also you're more than welcome this figment learn pathway will pay you

19. 8:03

    you know money and tokens uh you know something about 20 us dollars worth of tokens for 30 minutes of your time to try some code in fact everybody gets paid for finishing this course as well uh there's a some rates that we pay for participation and then prizes that we pay for you know winning demos at the end something like that sasha has the details on these maybe you can share them a little bit later or asynchronously

20. 8:28

    we have a bounties program where you can earn to solve our ideas we have some ideas um and so you know um a thousand near tokens or up to ten thousand year token something like that per bounty it takes some time to finish a grants program where you bring your ideas and we fund you know uh you know uh tens of thousands or uh hundreds of thousands of dollars worth of tokens to build out

21. 8:50

    uh you know new projects new products new features on the network openweb collective is like an incubator raised 15 million dollars for organizations that were teams that were going through that last year in 2020 and there's other things here you know bitcoin colonel for example has an eight-week fellowship if anybody's curious about that i have you know kind of access a discounted access to that program as well it's basically a eight-week boot camp to work with a bunch of entrepreneurs in the

22. 9:16

    web3 space on building an idea okay