From: Jeff King <peff@peff.net>
To: John Dlugosz <JDlugosz@TradeStation.com>
Cc: git@vger.kernel.org
Subject: Re: Presentation Ideas
Date: Fri, 17 Apr 2009 14:41:09 -0400 [thread overview]
Message-ID: <20090417184109.GA30489@coredump.intra.peff.net> (raw)
In-Reply-To: <450196A1AAAE4B42A00A8B27A59278E70AB285C4@EXCHANGE.trad.tradestation.com>
On Fri, Apr 17, 2009 at 11:29:36AM -0400, John Dlugosz wrote:
> I'm going to be giving a presentation on git to other development teams.
> Is there any good material around I can borrow from or use as
> inspiration?
There seem to be two popular ways to present git, and which you prefer
to see seems to be a matter of personal learning style. They are:
1. top-down; i.e., explaining commands in terms of workflow and
accomplishing user-oriented tasks, and trying to minimize details
unnecessary to the task at hand
2. bottom-up; i.e., explaining the data structures of git first, upon
which you can explain the behavior of commands, out of which you
can see how to piece together tasks.
I prefer (2) myself. It's a steeper learning curve, but I think it pays
off when advanced topics in git just make sense (but then, I also think
that normal users should understand sed and awk).
If you are interested in (2), I have often seen this page referenced:
http://eagain.net/articles/git-for-computer-scientists/
I also did a presentation of git to some CS grad students that was very
bottom-up. The slides are somewhat mediocre, but I would be happy to
share them if you like.
I think I stole a few diagrams from Junio's OLS talk, which has some
nice images (I especially like the symbolic view of the 3-way merge):
http://members.cox.net/junkio/200607-ols.pdf
-Peff
next prev parent reply other threads:[~2009-04-17 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 15:29 Presentation Ideas John Dlugosz
2009-04-17 16:45 ` Rostislav Svoboda
2009-04-17 18:41 ` Jeff King [this message]
2009-04-17 18:44 ` John Dlugosz
2009-04-17 18:51 ` Scott Chacon
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=20090417184109.GA30489@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=JDlugosz@TradeStation.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).