6 ms·

>As software engineers we've built lovely tools for ourselves (development environments, VERSION CONTROL, etc). Hmm, can't say I agree with your second point.

by leesec 5y ago

>As software engineers we've built lovely tools for ourselves (development environments, VERSION CONTROL, etc). Hmm, can't say I agree with your second point. The industry standard version control is notoriously messy and hard to work with.

animal_spirits 5y ago
AFAIK git was initially built to be a source control engine for other tools to build on top of, but most people have just used the underlying engine since it was easier. But I've really started to grok git after using a program called lazygit [0]. Basically a terminal UI on top of git where I don't have to remember the messy language of the engine, I just need to remember a couple of keystrokes. [0] https://github.com/jesseduffield/lazygit https://github.com/jesseduffield/lazygit
- thewakalix 5y ago
  Reminds me of how Lisp’s syntax was meant to be an intermediate format, but everyone found it intuitive enough that they didn’t bother writing the planned non-sexpr language.
  - RodgerTheGreat 5y ago
    perhaps you have heard of BANCStar: https://esolangs.org/wiki/BANCStar https://esolangs.org/wiki/BANCStar
  - deleted 5y ago
    [deleted]
- SilverRed 5y ago
  There are loads of UI layers over git. But largely the git cli is just better and more logical. Other than some minor weirdness, its a pretty good tool. The GUIs never expose the full power or standard error messages that the CLI will. Had a case where gitlab was blocking a push because the master branch was protected. The git gui gave the wrong error message about why the push was rejected.
dasil003 5y ago
Steep learning curve sure, but it's an extremely sharp tool that allows one to work magic once you're comfortable with it. After 1 year of git experience I could trivially do things that I never would have even attempted after a decade of CVS and SVN.
- hallway_monitor 5y ago
  Exactly. Anyone is free to continue using subversion but collectively we have decided the learning curve of got is worth the flexibility.
- LAC-Tech 5y ago
  > Steep learning curve sure, but it's an extremely sharp tool that allows one to work magic once you're comfortable with it. One of these years I'll be comfortable with git. Maybe next decade.
  - aynawn 5y ago
    This helped me learn git visually. https://learngitbranching.js.org/ https://learngitbranching.js.org/ You can probably complete that in less than a day
  - loopz 5y ago
    Make yourself your own git cheatsheet of what you need, and maintain it with examples from usage. It'll click in place and be useful.
    - LAC-Tech 5y ago
      have my own cheat sheet. it still hasn't clicked. I Just copy blindly off the cheat sheet. hopefully something better will come along.
      - loopz 5y ago
        But you get your job done? Git's just another tool. My guess is you've got bigger fish to fry.

by leesec 5y ago

animal_spirits 5y ago

AFAIK git was initially built to be a source control engine for other tools to build on top of, but most people have just used the underlying engine since it was easier. But I've really started to grok git after using a program called lazygit [0]. Basically a terminal UI on top of git where I don't have to remember the messy language of the engine, I just need to remember a couple of keystrokes. [0] https://github.com/jesseduffield/lazygit https://github.com/jesseduffield/lazygit

thewakalix 5y ago
Reminds me of how Lisp’s syntax was meant to be an intermediate format, but everyone found it intuitive enough that they didn’t bother writing the planned non-sexpr language.
- RodgerTheGreat 5y ago
  perhaps you have heard of BANCStar: https://esolangs.org/wiki/BANCStar https://esolangs.org/wiki/BANCStar
- deleted 5y ago
  [deleted]
SilverRed 5y ago
There are loads of UI layers over git. But largely the git cli is just better and more logical. Other than some minor weirdness, its a pretty good tool. The GUIs never expose the full power or standard error messages that the CLI will. Had a case where gitlab was blocking a push because the master branch was protected. The git gui gave the wrong error message about why the push was rejected.

dasil003 5y ago

Steep learning curve sure, but it's an extremely sharp tool that allows one to work magic once you're comfortable with it. After 1 year of git experience I could trivially do things that I never would have even attempted after a decade of CVS and SVN.

hallway_monitor 5y ago
Exactly. Anyone is free to continue using subversion but collectively we have decided the learning curve of got is worth the flexibility.
LAC-Tech 5y ago
> Steep learning curve sure, but it's an extremely sharp tool that allows one to work magic once you're comfortable with it. One of these years I'll be comfortable with git. Maybe next decade.
- aynawn 5y ago
  This helped me learn git visually. https://learngitbranching.js.org/ https://learngitbranching.js.org/ You can probably complete that in less than a day
- loopz 5y ago
  Make yourself your own git cheatsheet of what you need, and maintain it with examples from usage. It'll click in place and be useful.
  - LAC-Tech 5y ago
    have my own cheat sheet. it still hasn't clicked. I Just copy blindly off the cheat sheet. hopefully something better will come along.
    - loopz 5y ago
      But you get your job done? Git's just another tool. My guess is you've got bigger fish to fry.