Hi, in the last videos, we talked about the go path. In this video, we're going to be talking about how a typical NGO project is structured. So a typical NGO project has a parent directory called slash NGO, which has three sub directories, the source, the bin, and the package. All of our source code goes over here. So if you want to get started with the new go project, you simply create a folder over here. And as soon as you compile that folder, all of the compiled binaries are going to go inside this folder slash bin slash package contains all of the intermediate objects that are to be linked during compile time to create a self contained binary.

So I used a lot of jargons over here, so I'm just gonna step back and explain it to you step by step. So the go compiler has a function called the linker. So every time you compile your source code, it looks inside the package directory for prerequisites. And combining both of these two using the linker it creates a self contained binary. So that is a pretty good thing about go that all of its binaries are self contained. So I'm going to show you or demonstrate of the fighters Don't go, you just CD into your go path.

And you'll be able to see the source, the bin and the package. So if you go to source you'll be able to see all of the projects over here. And if you go to package you will be able to see all of the packages, the Linux AMD 64, dependencies and everything. And the bin. bin directory has all of the compiled binaries so you just do dot slash glide, or dot slash something to run it. So as we move along the further videos, in the more advanced section, we're going to be talking a bit more about the good on time and the go compiler.

Till then see