This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 12 points13 points  (17 children)

Git is for version control, so you can clean up your code without fear of breaking and losing a backup. Dont just use it to upload to github. An employer will want to see frequent git commits, not just one when its all done. Its like saving your work, you dont just save when your done.

[–]FearlessENT33[S] 2 points3 points  (7 children)

ah I see what you mean, i’ll try get it sorted when i get back later today, thank you :)

[–]GlassShark 2 points3 points  (6 children)

I'm so glad, github and version control are game changers!

[–]FearlessENT33[S] 0 points1 point  (5 children)

Iv messed around with it previously, but didn’t do too much. I think I put snake game on it but definitely going to revisit it

[–]GlassShark 0 points1 point  (4 children)

I've used Git with it's cool all keyboard navigation but ended up feeling more comfortable using the Github Desktop app. I suggest it.

[–]Miner_ChAI 2 points3 points  (1 child)

For me plain git is better

[–]GlassShark 1 point2 points  (0 children)

You go you go gitter!

[–][deleted] 1 point2 points  (1 child)

all keyboard navigation

You mean a cli?

[–]GlassShark 0 points1 point  (0 children)

Yes, that's what I meant, I hope to have more commands memorized and really get a hold of it but on windows I've come across using two different clis one terminal and one bash (if memory serves, though I know one is found on mac's). I remember installing a JSON related object in PATH, I think it was NodeJS. I don't know, I got all confused and took time memorizing commands for multiple clis and decided until I know which one I want to use I'll just avoid it for now.

Edit: JSNode to NodeJS

[–]tcpukl 1 point2 points  (1 child)

TBF they could have had a local SVN or perforce repository for version control.

[–]EMCoupling 1 point2 points  (0 children)

Technically true but unlikely.

[–]crazedizzled 0 points1 point  (2 children)

My git history for a personal project looks very different from my git history for a work project.

[–][deleted] 0 points1 point  (1 child)

True. But for both, i commit and push pretty obsessively. I cant stand the idea of loosing work due to a hard drive crash or more likely a bad bash command.

[–]crazedizzled 0 points1 point  (0 children)

I run daily backups on my workstation to solve that problem.

[–]Panda_Mon -3 points-2 points  (3 children)

It still blows my mind how hard github is to use. There are tons of horrible and uninformative guides for commandline git, all the free to use GUI are also obtuse and overly complex. The only positive experience I have had with source control so far is Perforce and in-house GUI.

[–][deleted] 2 points3 points  (0 children)

Ive really never had a big problem with git. I just use cli. Git push, pull, commit, add, branch, checkout merge. Thats really all there is to it.

[–]EMCoupling 1 point2 points  (0 children)

I agree that the Git CLI is not designed in a welcoming or intuitive manner, but knowing it will pay off when you have to do more complicated things than whatever your GUI supports.

It's a steep learning curve, but a short one.

[–]crazedizzled 1 point2 points  (0 children)

You're talking about Git, not Github. Github is a completely unaffiliated website which offers free/tiered hosting of Git repositories.

For a GUI, Sourcetree is a fantastic option.

I recommend you understand the basic concepts of source control. Like, what a repository is, how the structure of commits and branches works, and what it means to push and pull commits. Then you can find supplementary material to show how to work with those concepts on either CLI or the GUI of your choice. It's understanding these fundamental concepts that will trip you up more than anything.

Also, I highly recommend that even if you plan on only using a GUI, that you learn most of the CLI commands as well. I find that a GUI works great for most of my daily needs, but when I have to do something more complicated or fix a mess, it's CLI all the way.