NEAR NEAR Certified Developer, 14 Jul 2021

Previous Meeting

⏯

youtube image

►

From YouTube: L1C4 - What is This NEAR Developer Certification

Description

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: http://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: https://near.org/
Discord: https://near.chat/
Blog: https://near.org/blog/
Twitter: https://twitter.com/NEARProtocol
GitHub: https://github.com/near https://github.com/nearprotocol
#Blockchain #FutureIsNEAR #NEAR #nearprotocol

A

Okay, so briefly, here, let's agree on a path: uh we're going to be doing this stuff on the left. Testnet localnet betanet like stuff that, on the left-hand side, we're not going to be digging into mainnet, except I'm going to try and get everybody to deploy a mainnet application in the next 24 hours, actually that we can use to interact with each other. I've just written something over the weekend that I think, might be fun I'll, try and convince you that we should try and deploy it.

A

uh And then maybe you know a third of people in the call will be able to to do it and and other people might be incentivized to catch up, because uh you know we'll be able to share in this experience together. I'm not gonna reveal what it is until we're actually looking at it. um So we will be talking about contract literacy, not contract security, right there's, not a lot of stuff that we're we're digging into with contract security.

A

So just heads up, um we could talk about nfts and fungible tokens and the standards that we have for that and examples that we have, but we're not going to be talking about. Like token economics, some people really get into that sort of stuff and like how do we design this and there's all sorts of tools for modeling token economics and human behavior around that? I'm not going to touch it near core contracts we'll be talking about, but not sort of moonshot things like?

A

Can we port uniswapped in here like if you gave me a week, I'm not sure if I could even estimate that I'm not really sure what that would take uh but feel free to ask these questions. But you may not get the answer here in this uh in this experience. Okay, just just heads up on that and then cross-contract calls ability to communicate from one contract to another. This is really near's scalability story.

A

So, as your contract is running, you might fire off three or four other calls to contracts which then come back like asynchronous programming, process-based programming in javascript. You can think of it and it has some similar kind of feel to the code. It feels a little bit similar to that, but we're not going to be talking about the you know: consensus model and sharding compute and storage and and sort of the protocol underneath at all, that's out of scope and I'm not qualified to talk about it.

A

uh Yeah so uh nikhil is asking every function, call gets 200 milliseconds, it gets 200, tera gas and uh you know one tera gas is about one millisecond more or less on the wall clock. So the goal is we want to have the block ticking over once every second of clock time, and so that means we have about a thousand milliseconds in that one second, depending on the block time.

A

Actually it may grow shrink a little bit may increase a little bit so 200 milliseconds, 200 tear gas is good enough to allow a little bit of overhead for cross-contract calls and then a little bit more overhead for the communication around shards and kind of the gossiping of the state of the network.

A

So that's why 200 milliseconds is so small all right and we can. We can dig into that. If you like yeah and so we've got. You know these meetings. I think it's 4 pm utc. We started today right so every single day, starting at the same time today, 60 minutes max 120 minutes uh friday, uh 60 minutes as well. um Every day it's about 30 to 60 minutes depends on how many questions you've got. We've got synchronous activities.

A

That's you know this kind of stuff, maybe talking about process or aha moments or whatever demos on friday and then lots of asynchronous activities, lots of work on your own again as a junior dev, you should be budgeting six to ten hours a day, and I'm not saying this like, oh, maybe I'll, just put in an hour or two it'll be fine. It won't be fine.

A

It's a lot of work, so brace yourself. Okay, I'll just remind you, and if you don't have time to do it this week, that's fine, try again in a couple of weeks, okay, so demonstrations. What are those on friday? This is what you need to build. So, at the end of the week, I'm expecting from you contracts in rust, assembly script or both.

A

Maybe you want to have contracts that are collaborating unit tests for those simulation tests mock-ups only for the front end, they could be hand-drawn or using balsamic or something but don't implement the front end avoid that temptation. If you can and a documentation of course that looks like the stuff on the right-hand side. You can barely read it, I'm sure, but these slides are available. This slide hasn't changed for all four of these presentations, and the idea here is that this nearly neighbors, for example, is like a kickstarter for your neighborhood projects.

A

You might say I want a coffee shop. You know within a one mile radius of my house and I'm willing to put a hundred dollars in as an early investor in that it gets locked up somewhere. When the proposal hits its. You know, threshold for minimum, you know capitalization, then it automatically creates a project that manages the construction of that coffee shop.

A

Let's say, uh and then you know when you show up in the coffee shop you get recognized because you know your account is registered there on the chain for your free coffee, you know a year's worth of free coffee or whatever. That is right, so this is the idea of this project and it's a complete project. In that sense, there are some placeholders here and there some some rough edges here or there, but this will give you a sense of sort of the scope of what we're expecting on friday.

A

Okay, there are other examples as well three sample projects uh and now I think, uh more than four demo projects, maybe almost ten demo projects like nine or ten demo projects. So I need to update this slide. Actually, um let's make that nine demo projects and if you click on this link, it should open up the ncd filter. Here you can see one two, three, four, five, six, seven, eight nine projects these are: these are demo projects. I think you can see that okay right, these are demo projects in the learn near organization.

A

Here's the url to see these demo projects.

A

So if you want to see what other people have built, go for it all right so and now there's actually, I think four sample projects as well, um but uh we can talk about that in a minute. Okay, so these are this. This is this library will continue to grow the way this works is when you give the demo at the end of the week. I ask you to submit your url and then I fork it into uh this um into this organization.

A

So we can keep track of what you've produced for your demo right. So you put it anywhere, you want and then we'll fork it in. You can see all these ones.

A

On the right hand, side are forked in here and then the ones on the left, I've written myself or or with cl in collaboration with other people right somehow, okay, so hopefully that gives you a good sense of the demos and the scope and where you can find these, it's going to be an intense week, brace yourself I'll say that again, okay, so what kind of changes hajjar is asking? Are we expected to do ajar? I don't quite understand what you mean by changes. You're expected to do.

A

Can you clarify that either verbally or in in text? Can you explain what you mean? What kind of changes are we expected to.

A

Do okay, so you're, not speaking up, so I assume that you'll do it uh by text, but I'm not quite sure what you mean. If anybody else knows what she means by this, please uh let me know and then flex 13 is saying to deploy a code. What should I do on ubuntu yeah? So we'll talk about deployment for sure, so no stress we'll walk through the steps of all this stuff and help you with it. There's no rush. You don't need to do it right now.

A

Okay, so defining success, uh yeah of course. um So this course l1 is what this week ends. You you finish the course with a demo. L1V is 60 minute code interview with me or any other qualified code reviewer. The team will grow to be able to do that. Maybe you want to be a code reviewer for future cohorts. We can have that conversation as well, but at a minimum you would need to know enough to be able to make a judgment about whether someone's understood what it is they've done.

A

So I'm the only one who's doing that right now and maybe others internal veneer will be invited to do that. But eventually I would like to see some of the graduates of this program also help cover some of that as a peer review.

A

Okay, so sorry, just to cut off here hijar's is, is clarifying additions to the contract. So what kind of changes are we expected to do in terms of additions to the contracts? Thanks to jar, for clarifying so you're expected to write your own contracts from xero from a blank file actually to write your own contract set up your own project, deploy? It include unit tests simulation tests, documentation front end the whole deal if you've been to a boot camp. It's like a final project in the boot camp, but I don't need the front end.

A

I would prefer designs unit tests simulation tests, a working contract on technology that you're, maybe only seeing for the first time today, it's not going to be an easy week. I'll say that again, it's a lot of work. This week it's going to be intense, okay, I believe, if you're committed to it, you can do it. That's no problem, okay and level. Two and level three are. Basically. You know these numbers, I'm not really sure we're still figuring out exactly what constitutes level two or level three in terms of the size of your applications.

A

Maybe some of you will have mainnet applications in a week or two. uh That would be amazing, uh but for now this is kind of the notional idea and if you're curious about sort of the sketch for what these uh courses uh this level uh compares to the next two levels of courses, I'm happy to share that with you and for the time being, all these courses are either free or paid. Eventually, in the future we might charge for these things. It depends on on what we decide to do with this all right.

A

So um then, what what can you do after this people always ask what, after what? What can I do next, so you can check out near.academy. You can do that today. If you want, in fact you don't need to wait. Near.Academy is a url. It's a very simple, eight chapter walkthrough, you can take a look at the code, read some stuff and it will walk you through the meme museum actually, which is, uh on the left hand, side.

A

You can see that the middle project here sample meme museum, that's near academy, the code behind that figment, learned pathway, you get paid something about 20 bucks to spend 30 to 60 minutes learning about near code, uh the bounties program. You can earn more money solving our problems, the grants program. You can earn money, solving your own problems of your own design and the open web collective. You can join startups that are building. uh You know businesses there. So this is what you could do next in.

A