Presentation Ideas

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?

--John

TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.
  If you received this in error, please contact the sender and delete the material from any computer.

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?

Just show them the two videos from http://git-scm.com/documentation
The one with Linus is really ... :) well let's call it 'entertaining'

Bost :)

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

I think my audience needs to be shown what git can do for them, and why they should want to use it, as opposed to how to drive it or how it works under the hood.

Thanks for the links.

--John

-----Original Message-----
From: Jeff King [mailto:peff@peff.net]
Sent: Friday, April 17, 2009 1:41 PM
To: John Dlugosz
Cc: git@vger.kernel.org
Subject: Re: Presentation Ideas

On Fri, Apr 17, 2009 at 11:29:36AM -0400, John Dlugosz wrote:

quoted

I'm going to be giving a presentation on git to other development

teams.

quoted

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

TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

On Fri, Apr 17, 2009 at 11:41 AM, Jeff King [off-list ref] wrote:

On Fri, Apr 17, 2009 at 11:29:36AM -0400, John Dlugosz wrote:

quoted

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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

I have put a number of my presentations online at

http://github.com/schacon/git-presentations

There are four in there now, but I'll add the one I'm giving at
RailsConf in a few weeks once it's completed.  Most are high level or
top-down, the railsconf08 is more bottom-up.

Scott