git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git top links: 2010-7
Date: Sun, 18 Jul 2010 06:23:13 -0700 (PDT)	[thread overview]
Message-ID: <m3eif0ncva.fsf@localhost.localdomain> (raw)
In-Reply-To: <AANLkTilmTwl9RaX31MDmVY3YCeATg5RKF3RQbNqb3Soq@mail.gmail.com>

Felipe Contreras <felipe.contreras@gmail.com> writes:

> 6. Distributed Version Control is here to stay, baby (14)
> A story of why Stack Overflow's podcast regarding DVCS was plain wrong
> http://www.joelonsoftware.com/items/2010/03/17.html

And if you read this blog post carefully, you would see that Joel
still doesn't f***ing get it.

> 9. Git for the nervous developer (10)
> Explaining git from a convert
> http://beust.com/weblog/2010/04/06/git-for-the-nervous-developer/

This quote from abovementioned blog is especially apt

 "Here is an analogy that might help, though: to me, learning Git is
  very similar to learning a foreign language. Natural languages are
  notoriously hard to learn for adults because their organic growth
  has resulted in all kinds of inconsistencies and oddities. At the
  end of the day, the only way to learn a foreign language is to
  memorize, memorize and memorize. As years go by, practice make
  memory regurgitation more automatic and the use of that language
  requires less and less conscious effort, but the learning curve is
  something that just can't be avoided."

The Git UI was result of organic growth.  It is not as much as it was
designed, rather than "happened".

-- 
Jakub Narebski
Poland
ShadeHawk on #git

  reply	other threads:[~2010-07-18 13:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-16 23:16 git top links: 2010-7 Felipe Contreras
2010-07-18 13:23 ` Jakub Narebski [this message]
2010-07-18 17:46   ` Felipe Contreras

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3eif0ncva.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).