8 ms·

I learned how git works but without my cheat sheet and scripts I am a helpless angry baby. (guess where I keep them? git) Still I happily award the Cryptic Wei

I learned how git works but without my cheat sheet and scripts I am a helpless angry baby. (guess where I keep them? git) Still I happily award the Cryptic Weirdo Savant of the Year Trophy to anyone who can convincingly lie about memorizing that gibberish.

olddustytrail 4y ago
You clearly didn't learn how it works since you're helpless without a cheat sheet. Sounds like you memorized some stuff. I didn't memorize it, I learned how it worked. These are very different things.
- kerblang 4y ago
  That was mildly convincing but it's been a fairly competitive year
  - olddustytrail 4y ago
    It's not because I'm super smart, you're just super lazy.
    - AnimalMuppet 4y ago
      Personal attacks are against the site rules here.
  - lolc 4y ago
    Cute. I typically use an array of Git commands per hour of working. I consult the manual or a how-to maybe once every other week. Re-cloning a repo happens less than once a year for me. Can't remember the last time I had to do that. And it's not just me. I see the same for the people I work with. Of course, for many people, learning Git is not worth the effort. But that doesn't mean people who handle it fluently don't exist.
- kerblang 4y ago
  Okay let me actually return to the point. I practically spelled it out already, but why would I need a cheat sheet if I "memorized some stuff"? Why would I accuse anyone claiming to memorize this "stuff" of lying if I actually memorized it? Let's think hard here. cue jeopardy theme (i just had to google "jeopardy" because I can't remember how to spell it! But I know how to play!) (but they won't let me) I mean yes I am a lazy idiot but I'm not that self-contradictory. Okay i am done with this. Done done. Go flame.
dotancohen 4y ago
Feel like sharing your cheat sheet? I've been using git for over a decade but I find that personal cheat sheets are still a valuable resource.
- kerblang 4y ago
  An easy request to fulfill so https://github.com/zaboople/techknow/blob/master/git/git.txt https://github.com/zaboople/techknow/blob/master/git/git.txt Although there is some garbage in there that I just ignore instead of cleaning up. Perhaps useful as a meta-tutorial on maintaining a cheat sheet though: Store it in a github-like repo of its own so that you can download it anywhere, update it, etc. I also have an equally unhelpful but meta-helpful series of scripts prefixed with "gip-" (pig backwards) in here: https://github.com/zaboople/bin/ https://github.com/zaboople/bin/ This is cheat sheet plus one: At some point you might as well make a script for it rather than digging it out of your cheat sheet. In fact I'm kind of pursuing this idea of "instead of one command with 1000 options, why not 1000 commands?" I think there's maybe a way out of git hell in that idea...
  - dotancohen 4y ago
    Some real gems in there. I could only imagine how you got to the point about worrying about umask - maybe reusing some directory that was holding old code experiments before? As for all the grep scripts, you might want to take a look at rip-grep, it lets you filter on file type. Thank you!

olddustytrail 4y ago

You clearly didn't learn how it works since you're helpless without a cheat sheet. Sounds like you memorized some stuff. I didn't memorize it, I learned how it worked. These are very different things.

kerblang 4y ago
That was mildly convincing but it's been a fairly competitive year
- olddustytrail 4y ago
  It's not because I'm super smart, you're just super lazy.
  - AnimalMuppet 4y ago
    Personal attacks are against the site rules here.
- lolc 4y ago
  Cute. I typically use an array of Git commands per hour of working. I consult the manual or a how-to maybe once every other week. Re-cloning a repo happens less than once a year for me. Can't remember the last time I had to do that. And it's not just me. I see the same for the people I work with. Of course, for many people, learning Git is not worth the effort. But that doesn't mean people who handle it fluently don't exist.
kerblang 4y ago
Okay let me actually return to the point. I practically spelled it out already, but why would I need a cheat sheet if I "memorized some stuff"? Why would I accuse anyone claiming to memorize this "stuff" of lying if I actually memorized it? Let's think hard here. cue jeopardy theme (i just had to google "jeopardy" because I can't remember how to spell it! But I know how to play!) (but they won't let me) I mean yes I am a lazy idiot but I'm not that self-contradictory. Okay i am done with this. Done done. Go flame.

dotancohen 4y ago

Feel like sharing your cheat sheet? I've been using git for over a decade but I find that personal cheat sheets are still a valuable resource.

kerblang 4y ago
An easy request to fulfill so https://github.com/zaboople/techknow/blob/master/git/git.txt https://github.com/zaboople/techknow/blob/master/git/git.txt Although there is some garbage in there that I just ignore instead of cleaning up. Perhaps useful as a meta-tutorial on maintaining a cheat sheet though: Store it in a github-like repo of its own so that you can download it anywhere, update it, etc. I also have an equally unhelpful but meta-helpful series of scripts prefixed with "gip-" (pig backwards) in here: https://github.com/zaboople/bin/ https://github.com/zaboople/bin/ This is cheat sheet plus one: At some point you might as well make a script for it rather than digging it out of your cheat sheet. In fact I'm kind of pursuing this idea of "instead of one command with 1000 options, why not 1000 commands?" I think there's maybe a way out of git hell in that idea...
- dotancohen 4y ago
  Some real gems in there. I could only imagine how you got to the point about worrying about umask - maybe reusing some directory that was holding old code experiments before? As for all the grep scripts, you might want to take a look at rip-grep, it lets you filter on file type. Thank you!