What code should you open source?
That is a great question.
So when we create a new repository and we will create a new repository, I'm just going to show you
here, just as a glimpse into the future, we can have a public repository so everyone can see our code
or a private repository where only we can see our code.
And there's a use case for both of these.
So if I go over to my account, GitHub, dotcom, slash Caleb Torline and just go into my repositories,
054 repositories, that's quite a bit.
You can see that I actually have.
A repository already is the first one that shows up, it's private, it's just called school.
And then I have some other ones that are completely public, so like get essentials, which is what
your project is going to be in Git and GitHub to a one, I believe there's Django to a one.
So the source code for Django to a one, we could go and see all of the permits in here.
This is all the step by step instructions for the Jianguo to a one module, and so the idea that I want
to talk about in this lesson is what code should you open source?
And so, in my opinion, open source as much as possible.
The world has thrived off of open source and you wouldn't believe it.
But almost everything comes from open source.
Almost every website you you hit, every website that you use is using Linux behind the scenes, completely
open source, 100 percent free.
If you write Django like I do, completely open source, one hundred percent free.
And so the idea is to perpetuate or to move that momentum forward by creating more open source stuff.
And so pretty much any project that you have, I would say make open source if you can.
The other question I guess we should tackle is what should you make private?
And so I'm working on a project.
Codename school, and I don't want it to be public, I don't want everyone to see the source code,
I want it to be a little more proprietary.
And the idea is I'm going to be building a company around this and I don't want other people being able
to steal that code.
I want to be able to create a for profit business using this code in here.
But for example, get essentials is completely open.
Source is to commit sin here and.
It's completely.
Available, you can see all the comments, you can see everyone who's contributed, you could see all
the different poll requests, you can see all the different issues, you can see all different things
in here.
And so when you're going to work on a project, I would highly, highly, highly recommend that you
make it open source just because primarily when you go and look for a job, someone who is interviewing
you is surely going to Google your name.
And if they can find you on GitHub and see that you can use get B can use GitHub so you know how to
open source code, that is a strong indicator to them that you are a decent developer and that they
should, in fact take you seriously.
I would say open source as much as possible, as much as humanly possible.
There are cases where you don't want to open source, but for the most part, pretty much all of my
code is open source.
I have very few things in here that are private.
I've got a client, presidential, auto, private.
They paid for that.
The repository for lern wagtail dot com, it's a security thing.
It's private, but everything else is public, and so you can see most of my stuff is public, it's
all open source.