L1C2 - What is This NEAR Developer Certification
Nothing is loaded from YouTube until you press play, and then without tracking cookies.
About this video
NEAR Certified Developer
This course is an opportunity for web developers to earn a Certificate of Completion that represents the ability to design, develop, test and deploy smart contracts on the NEAR platform.
Slides: bit.ly/near-ncd
Overview
During this course we practice the following:
perceiving web 3 in the context of human history reading contract code in Rust and AssemblyScript writing contracts using Rust and AssemblyScript testing contracts using unit and simulation tests deploying contracts and a sensible user interface
---
Follow the latest from NEAR Protocol on: Website: near.org Discord: near.chat Blog: near.org/blog Twitter: / nearprotocol GitHub: github.com/near github.com/nearprotocol #Blockchain #FutureIsNEAR #NEAR #nearprotocol
Transcript
1,316 wordsCaptions as YouTube publishes them, usually machine-generated, so product and people names can be misheard.
- 0:09
now let's agree on a path actually what's in and what's out we're going to be talking about testnet localnet and betanet we're going to be talking about contract literacy nfts and funchable tokens core contracts cross-contract calls all that is in this week but what's out this week mainnet we're not going to be talking about deploying the main net because there's more that you have to do
- 0:33
if you really want to deploy a trustless application you need to manage your keys and remove them in that way the contract can't be modified for example you've got to figure out what to do with the money that that contract might collect or control identities and so on there's all sorts of details on mainnet that are outside the scope of this conversation but we have several applications deployed on mainnet and so if you're curious if you're ready to do that more power to you that's fantastic but
- 0:56
we're not going to dig into that together this week we're also not going to talk about contract security because there's all sorts of little details about how contract security works that are outside the scope of this week so maybe another week or maybe another month of work together might give us access to building for mainnet talking about contract security token economics and what it means to actually design for incentivization
- 1:18
mechanism design and so on we're not going to talk about any moonshot ideas like i want to port una swapped in here good luck to you but it's not going to happen in a week if you gave me a week i might not even be able to tell you how long it would take me to do it and we're not going to talk about sharded compute and storage in terms of the details remember the battery that we saw before the car engines that we saw before we're not going to dig into those details
- 1:42
we're going to stay up here to talk about reading writing testing and deploying contracts this is the schedule for the week every single day today's our first we're going to have meetings at 3 pm utc monday's 60 minutes friday's 60 minutes every other day is 30 minutes during these meetings today is our kickoff welcome and kickoff and then fridays are demos and we'll say goodbye and tuesday wednesday and thursday we might talk a little bit about process answer some questions share some share
- 2:14
some aha moments and we'll have 30 to minutes to two hours to do that together no problem at all and the goal on a daily basis is today there's work to do you should be reading contracts and if it's very late for you for example then start early tomorrow you should be reading contracts writing contracts tomorrow testing contracts then deploying and finally demonstrations on friday
- 2:37
this is what you'll demonstrate something like this so several people were asking what are we gonna learn this week what are we gonna submit in a week this is what you're gonna submit this is the answer to your question at the end of the week each small group is going to present a project of their own design and development and the scope is defined by this example there's a repo here that you'll find this gives you an idea it's going to include contracts
- 3:01
rust assembly script maybe both maybe a mix unit tests simulation tests just the mock-up please ignore the temptation to build a front end you can if you want to but ignore the temptation because that's the easy work it's it's tempting to focus on the thing that we know to ignore the difficult part instead stay confused this week focus on the most difficult aspect of the work this week focus on the contracts reading writing testing and deploying them and then documentation exactly as you see here
- 3:33
build tests explanations the example story proposal this may be a little bit too small for you to read but the idea is you can see this repository and see exactly what i'm hoping every single group by the end of this week will produce you don't have to do this as an individual you can if you want to but you don't have to but as a group i expect you'll be able to ship something like this and demonstrate it to us actually last time we ran this
- 3:56
uh one person one group sorry a team of four or five people was able to build actually a working demo by friday but they had already experienced building with near a couple of people and so for them they were building it was an exercise essentially there was another person who was able to produce this level of work in a week and they had never built anything on near before and they did it
- 4:19
in assembly script so my recommendation is stay modest stay to this focus come up with an idea more than happy to help you with that you can certainly ask other people for it we have lots of examples that we can talk about contracts unit tests simulation tests mock-ups not the front-end working mock-ups and documentation and if you want as a moon shot as an extra step as a bonus you can try building the front end but i
- 4:43
would wait until the very last minute to think about that because that's the easy stuff all right so the measure is can we learn from it and here's basically this kind of defining what success looks like here's the list l1 that's this supporting others and learning while you learn to you have this certification after completing the course and you keep the certification as long as you continue to help others
- 5:06
and to continue to learn that's how this works it's about evidence all right um for l2 build and deploy a test net app that grows to 100 users and for l3 build and deploy a mainnet app that grows to a thousand users and and these are still under heavy development here so you know if you have some better ideas about how we should kind of measure levels of certification the goal is to make it matter it should mean something
- 5:30
and it should also be achievable so there's a balance there right so so this is you know our current estimate here for l1 that's this course it's about finishing this course all the way to the end producing that demo and then to keep the certification continuing to learn continuing to help people in the community and lean into this work together and then what maybe after this course what can you do you can go
- 5:54
and go through the figment learn pathway you know we'll pay you 20 in your tokens for 30 minutes of your time uh this course is also paid by the way we have a bounties program where you can solve problems that we've listed for you know a couple of thousand uh near tokens uh uh or a couple thousand dollars in your tokens uh and it takes several days maybe a month or so to solve those depending on the boundary could be more grants program applying
- 6:18
you know 10 thousand up to a hundred thousand dollars uh in grants for three to six months of work depends on the amount of work there the open web collective raised collectively 15 million uh dollars us dollars last year um and then get coin kernel is this eight week program there's another one that starts in march if you're curious i can send you an invitation please let me know so these are some of the things that you
- 6:39
can do next what next