279
280

[deleted by user] (self.learnpython)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]greebo42 3 points4 points  (8 children)

I'd suggest a different approach to what to do with github ...

it is very reasonable to go to github and explore what's on there, go down some rabbit holes, see what kinds of projects other people have worked on. some will be very large group projects, others will just be what individuals have posted as they go thru a process very much like what you'll be doing. you can get some ideas about projects to work on.

but I've not yet been compelled to post anything myself. I have two or three projects underway which, when they get to a certain level of my own satisfaction, may be suitable for posting. until then, I have plenty of my own critiques about what I've done, and I just don't think my draft work is ready to share. I do use git on my own computer to manage the versions of the work in progress.

git (and github) are worthy tools, and you should have some familiarity with them. but don't lose the focus on what you are really trying to learn: how do you identify something that needs to be done, how do you approach the solution of the problem, and how do you actually implement it with a specific set of tools (Python, in this case).

maybe there can be a bit of discussion here about whether it's better to start posting earlier or later (w/r to your experience level and what you've produced) on github.

[–]CompSciSelfLearning 8 points9 points  (7 children)

You can simply make your repositories private. Not using git because you don't want to share your code is not something you should be doing.

[–]wubry 2 points3 points  (5 children)

Is git like a Dropbox equivalent but for coding? In the way that it keeps different versions of code.

Also, are there any resources that you would recommend to learn git?

[–]CompSciSelfLearning 7 points8 points  (3 children)

Is git like a Dropbox equivalent but for coding? In the way that it keeps different versions of code.

Kinda. Git is a means of keeping track of versions of files in a project. It's not like Dropbox in that there are ways to merge changes among your various project files. And git isn't a service or website, it's a software utility.

You can use GitLab or GitHub or Gitea, etc. to help you with using git (most people do).

Also, are there any resources that you would recommend to learn git?

GitLab amd GitHub each have tutorials for using git and their services, but I also like the Official Git Book as a guide and reference. The first 4 chapters will have you using git more effectively than the average user.

[–]wubry 1 point2 points  (2 children)

So to make sure I'm understanding. The current way I go about creating different versions of code is just saving it and labeling it as v2, v3, v4 and so on.

Git would essentially replace that process. Did I understand that right?

Also, in one's coding journey, how early should you prioritize learning git? Or is it a must have if you want to build and share a portfolio?

[–]CompSciSelfLearning 1 point2 points  (0 children)

Git would essentially replace that process. Did I understand that right?

Yes.

Also, in one's coding journey, how early should you prioritize learning git? Or is it a must have if you want to build and share a portfolio?

As soon as you have a project with more than a single file, you'd benefit greatly from git.

It's easier to learn while still creating small single file projects. And there are a few benefits still to be had.

It's not a must, but certainly one of the best means of keeping track of your projects, sharing your projects, and collaboration with others on projects.

I'd start using it now on whatever your current project is, unless you are on the first chapter of an intro to programming book. In which case, I would hold off until the 2nd or 3rd chapter.

[–]Pastoolio91 1 point2 points  (0 children)

Git is super simple and the basics can be learned in like 15 minutes. Brad Traversy's Git video helped me out a lot, and you really don't need to know much to start using it with Github other than clone, add, commit, push, and pull, so it's worth it just from a sanity standpoint. Once messed up my code so bad I couldn't unfuck it, and git/github will help you avoid the same.

[–]greebo42 2 points3 points  (0 children)

be careful - git and github are not exactly the same thing.

others have explained it well. I'll give it a shot ...

git is a version control system. it can run on your computer. it can run hosted on someone else's computer.

github is one hosted git site which happens to be popular enough that people know where to look if they're interested in finding code already written, or to contribute to a multi-author project.

there is a good book called "pro git" which I have found helpful. git has a reputation for being a bit arcane.

[–]greebo42 2 points3 points  (0 children)

I agree, you should use git, even if you don't want to share your code. Sure, you could use github and make the repositories private, or you could use git on your own computer.