5 ms·

This is one of those "explanations" where, if it's a concept I'm familiar with I can apply my knowledge to it and see that it mostly checks out, but if it's som

This is one of those "explanations" where, if it's a concept I'm familiar with I can apply my knowledge to it and see that it mostly checks out, but if it's something I don't already know, I find completely useless.

tempodox 5y ago
Agreed. Explanations of git sometimes remind me of monad tutorials.
- contravariant 5y ago
  I suppose you could combine the two by pointing out that git is like a category where a git merge is like a pushout etc.
- lvass 5y ago
  Git is simply a directed acyclic graph of commits with pointers, stashes, a few named data stores and two quasi-recursion mechanisms.
  - tempodox 5y ago
    “A monad is just a monoid in the category of endofunctors.”
- CrazyPyroLinux 5y ago
  "It's like a burrito!"
  - PebblesRox 5y ago
    For the unfamiliar: https://www.google.com/amp/s/byorgey.wordpress.com/2009/01/12/abstraction-intuition-and-the-monad-tutorial-fallacy/amp/ https://www.google.com/amp/s/byorgey.wordpress.com/2009/01/1...
isaacimagine 5y ago
Personally, as someone who has been sketchnoting for about 5 years, I feel the point of sketchnoting is more to create a condensed visual reference of an idea for personal recall than for teaching that same idea to someone else. There's a wider argument here of whether notes should be used for personal recall or general reference. I tend to lean towards the former, but there's more nuance here. I'm working on a blog post that discusses how to take good sketchnotes and breaks down this argument a lot further, but it's already super long and far from being finished... perhaps I'll finish it someday, haha. Kudos to the original author of these notes. When taking these types of notes, you have to think about what to leave out as much as what to leave in. I think that concise notes in this style to show that the author has a deeper understanding of the subject than the notes convey on the surface, especially when the point of these notes are to compress one's knowledge on the subject into a concise visual representation. Sketchnotes are macroexpand for the brain :P
shimonabi 5y ago
Exactly. I use basic git daily, but I'm still confused about rebase.
- gfodor 5y ago
  I gave up. I determined some of us are just too stupid to do quantum physics or rebase in git without destroying our branch. I'm one of those people.
  - mhh__ 5y ago
    FWIW Git is harder to understand than basic quantum mechanics IMO. The latter has been optimized with good notation and has a fairly simple structure, whereas Git is a beautiful idea wrapped in an API from hell
- frutiger 5y ago
  Rebase is copying a series of commits and pasting them onto somewhere else. By default it will copy commits and apply them onto the new upstream. In other words, go from old your master master ----*----*----A----B----C----D \ \ new \ master \----*----* to old your old master master ----*----*----A----B----C----D \ \ new your \ master master \----*----*----A'---B'---C'---D' Interactive rebase allows you to choose to reorder, rename, combine or drop those commits A, B, C, D as they are applied to new master.
  - deleted 5y ago
    [deleted]
- stinos 5y ago
  For me it's the other way around. I mean, it's like one of the few commands which says what it does: re-base. Makes all kind of sense to me: take what you have and put it on top of something else. So same as a bunch of cherry-picks, etc. It was one of the first concepts I undesrtood. Merge on the other hand I understand as well but it leads to graphs I can't understand without spending some time looking at.
pelagic_sky 5y ago
As a designer. I don’t understand these. I know the overall concept of using git but this didn’t bring me any aha moments.
deleted 5y ago
[deleted]
deleted 5y ago
[deleted]

tempodox 5y ago

Agreed. Explanations of git sometimes remind me of monad tutorials.

contravariant 5y ago
I suppose you could combine the two by pointing out that git is like a category where a git merge is like a pushout etc.
lvass 5y ago
Git is simply a directed acyclic graph of commits with pointers, stashes, a few named data stores and two quasi-recursion mechanisms.
- tempodox 5y ago
  “A monad is just a monoid in the category of endofunctors.”
CrazyPyroLinux 5y ago
"It's like a burrito!"
- PebblesRox 5y ago
  For the unfamiliar: https://www.google.com/amp/s/byorgey.wordpress.com/2009/01/12/abstraction-intuition-and-the-monad-tutorial-fallacy/amp/ https://www.google.com/amp/s/byorgey.wordpress.com/2009/01/1...

isaacimagine 5y ago

Personally, as someone who has been sketchnoting for about 5 years, I feel the point of sketchnoting is more to create a condensed visual reference of an idea for personal recall than for teaching that same idea to someone else. There's a wider argument here of whether notes should be used for personal recall or general reference. I tend to lean towards the former, but there's more nuance here. I'm working on a blog post that discusses how to take good sketchnotes and breaks down this argument a lot further, but it's already super long and far from being finished... perhaps I'll finish it someday, haha. Kudos to the original author of these notes. When taking these types of notes, you have to think about what to leave out as much as what to leave in. I think that concise notes in this style to show that the author has a deeper understanding of the subject than the notes convey on the surface, especially when the point of these notes are to compress one's knowledge on the subject into a concise visual representation. Sketchnotes are macroexpand for the brain :P

shimonabi 5y ago

Exactly. I use basic git daily, but I'm still confused about rebase.

gfodor 5y ago
I gave up. I determined some of us are just too stupid to do quantum physics or rebase in git without destroying our branch. I'm one of those people.
- mhh__ 5y ago
  FWIW Git is harder to understand than basic quantum mechanics IMO. The latter has been optimized with good notation and has a fairly simple structure, whereas Git is a beautiful idea wrapped in an API from hell
frutiger 5y ago
Rebase is copying a series of commits and pasting them onto somewhere else. By default it will copy commits and apply them onto the new upstream. In other words, go from old your master master ----*----*----A----B----C----D \ \ new \ master \----*----* to old your old master master ----*----*----A----B----C----D \ \ new your \ master master \----*----*----A'---B'---C'---D' Interactive rebase allows you to choose to reorder, rename, combine or drop those commits A, B, C, D as they are applied to new master.
- deleted 5y ago
  [deleted]
stinos 5y ago
For me it's the other way around. I mean, it's like one of the few commands which says what it does: re-base. Makes all kind of sense to me: take what you have and put it on top of something else. So same as a bunch of cherry-picks, etc. It was one of the first concepts I undesrtood. Merge on the other hand I understand as well but it leads to graphs I can't understand without spending some time looking at.

pelagic_sky 5y ago

As a designer. I don’t understand these. I know the overall concept of using git but this didn’t bring me any aha moments.

deleted 5y ago

[deleted]

deleted 5y ago

[deleted]