12

As a Dev in college working for teams in college, I don't really have a need to use git, since most of 'self proclaimed prestigious programmer child prodigies' I work with have no idea what it is; but I use it anyways as good programming practice and ease of backups.

So I tried using a GUI client after months of the git bash, and even though I looked up a few tutorials (was embarrassed the whole fucking time). I ended up adding, committing and pushing via bash.

Can anyone explain me how is the GUI client helpful in large projects and stuff?

Comments
  • 2
    I never use it
    I will leave this comment here to get notifications
  • 2
    The only thing it may be useful for is visualizing your commit and branch history. For standard pull/push, nothing beats CLI.
  • 2
    As far as I can tell, two uses:

    Visualizing

    People who don't want to use CLI or likely are being dragged into using git kicking and screaming.
  • 0
    Visualizing and when I want to split changes in multiple commits (unless there are only a few add commands to run and I don't need to stage just part a file)
  • 0
    I only ever used the GUI as a learning tool - I've never seen a situation where using the GUI was more valuable than the CLI.

    If you're confident using the CLI, then stick with it. And don't forget to put that shit on your CV.
  • 0
    @Dotwo whoa, you mean putting git exclusively has a weightage? Or...Were you talking about CUI skills 😬?
  • 0
    I've been working with git since last 6 years on medium to big projects, never needed it. I've never heard any linux kernel developer using a git GUI client; and the linux kernel is a huge project.

    IMHO, the GUI clients are to sell to people who are scared of CLI.
  • 1
    @alcatraz627 Both, in fairness, but I would 100% mention git; knowing how to use version control is a big deal.

    Imagine being a manager hiring a graduate, and seeing a CV that says "You don't have to teach me this complex workflow pattern, I already know it." It's a big plus for getting an interview, and you can use it in the interview itself.

    My first interview after graduation, I brought up my Github account and walked through a project I was working on - I was able to show off the quality of my commenting, I knew how branches worked, my commit messages weren't arse, and that I could rebase successfully when shit went fanwards.

    It definitely helped me get that job.
Add Comment