News for hackers. Stuff that matters.
Re:Git Koans (2013) by positr0n on Wednesday January 11, 2017 @11:24PM (#13379817)
Either I don't get most of the koans or they are intended to disparage git's UX instead of truly enlighten. Is the joke just going over my head or am I not thinking hard enough?
Re:Git Koans (2013) by delecti on Wednesday January 11, 2017 @11:32PM (#13379849)
A Koan is "a paradoxical anecdote or riddle, used in Zen Buddhism to demonstrate the inadequacy of logical reasoning and to provoke enlightenment"

I think that kinda implicitly means the author considers git to be either paradoxical or illogical. That seems even more clear from the last two paragraphs of "The Hobgoblin".

Re:Git Koans (2013) by jejones3141 on Thursday January 12, 2017 @04:39AM (#13381017)
That's a reference to an Emerson quote; if I remember rightly it's "A foolish consistency is the hobgoblin of little minds". I suspect the implication is that only little minds expect consistency... but over and above Emerson being a questionable source for UI design principles, he qualifies it. The quote isn't "Consistency is the hobgoblin of little minds."
Re:Git Koans (2013) by th0114nd on Thursday January 12, 2017 @12:05AM (#13379940)
I didn't read the hobgoblin the same way as the author being purely critical. I read it as a defense: a similarity between commands would make it easier to choose the wrong one. Removing a branch is a more destructive than deleting a file, so it should be a command chosen with conscious care rather than muscle memory.
Re:Git Koans (2013) by sidhantgandhi on Thursday January 12, 2017 @05:33PM (#13386791)
That's the absolute opposite conclusion from what the author intended.
Re:Git Koans (2013) by adamrezich on Thursday January 12, 2017 @08:36PM (#13387748)
Are you the author? Or, if not, did the author specify their intended conclusions in additional material somewhere?
Re:Git Koans (2013) by lukeasrodgers on Wednesday January 11, 2017 @11:32PM (#13379851)
I can't speak for the author's intention, but yes, these "koans" highlight some of git's worst UX warts; or, arguably, not just UX warts but conflicts internal to the conceptual underpinnings of git (http://people.csail.mit.edu/sperezde/onward13.pdf).
Re:Git Koans (2013) by geezerjay on Thursday January 12, 2017 @12:52PM (#13384419)
> but yes, these "koans" highlight some of git's worst UX warts; or, arguably, not just UX warts but conflicts internal to the conceptual underpinnings of git

If that's the case, the "One Thing Well" kohan misses the mark rather glaringly.

Re:Git Koans (2013) by rtpg on Thursday January 12, 2017 @12:30AM (#13380017)
I feel like they're meant to be jokey about UX failings, but I'm unsure what the author is trying to convey.

For example:

> [something about history being present and immutable]

>“Splendid!” exclaimed the historian. “I have a historical record of a merge commit with two parents. How can I find out which branch each parent was originally made on?”

>“History is ephemeral,” replied Master Git, “the knowledge you seek can be answered only by the gods.”

the pedantic explanation here is that branches are a separate subsystem, with each branch just being a pointer to a commit. And the history works off of the commit.

The answer from "Master Git" doesn't feel like an answer from a master. Maybe I'm reading too much into this but Git becomes way less confusing if you think more about what things are, rather than how they're used .

Re:Git Koans (2013) by manicdee on Thursday January 12, 2017 @01:56AM (#13380329)
That is exactly the joke.
Re:Git Koans (2013) by hyperpallium on Thursday January 12, 2017 @12:36AM (#13380034)
git beats positr0n with its UX

at that moment, positr0n was enlightened

Re:Git Koans (2013) by treve on Wednesday January 11, 2017 @11:30PM (#13379842)
It is meant as a bit of a joke.
Re:Git Koans (2013) by rout39574 on Wednesday January 11, 2017 @11:29PM (#13379838)
Yeah, I read it as jeering, too.