search

ga-wdi-boston / git

Other
0 stars 107 forks source link

ga-wdi-boston/git #7

Open jrhorn424 opened 8 years ago

jrhorn424 commented 8 years ago

Summary

Using Git especially in the context of how we use them in the class.

Prerequisites

jrhorn424 commented 8 years ago

85 minutes actual

jrhorn424 commented 8 years ago

Previous actual was incorrect. I mistakenly lumped the time together with ga-wdi-boston/git-github-fork.

Actual was 65 minutes.

RealWeeks commented 8 years ago

70 minutes.

jrhorn424 commented 8 years ago

70 minutes is practically a 2 actual

berziiii commented 8 years ago

77 minutes actual (break included)

RealWeeks commented 8 years ago

70 inc break

jrhorn424 commented 8 years ago

I'm going to remove the prepared label until we've merged changes and closed other open issues. Apologies @payne-chris-r.

payne-chris-r commented 8 years ago

@jrhorn424 looks like this one is a "long 1 unit" (70+ is 2 units, correct?). Is it just that this is a "long 1" and github is a "short 1"?

jrhorn424 commented 8 years ago

I'll adjust the calendar. Thanks @payne-chris-r

payne-chris-r commented 8 years ago

1 Actual. 55 minutes. It went shorter than I anticipated, but went long on github lesson.

BenGitsCode commented 7 years ago

2 actual 80 minutes. Still think this is 1 actual. I went off script in the beginning and didn’t stay tight on time. This should be 1 block, I think my delivery and the size of the room contributed to the actual here.

MicFin commented 7 years ago

2 actual. Scheduled: 1-2pm Actual: 1-3pm (with two 10min breaks)

Spent more time explaining what version control and git are, why we use them, what they are similar to that we already know. There were MANY questions from the developers since some of them have experience with LM software that is similar. I was able to avoid most rabbit holes but still had to field questions and put them in perspective.

We made up to and including Stage 3 of http://learngitbranching.js.org/ and then encouraged them to do the rest on their own.

There was time spent drawing diagrams on the white board, potentially it would save time to have another consultant draw while the other presents. Also, having diagrams in the repository as image files or in the README could have been useful for saving time as well.

I think spending additional time on what git is was time well spent with this cohort and thanks to a well planned calendar we had the time available.

MicFin commented 7 years ago

2 actual. 120minutes. Scheduled: 12-1pm, lunch, 2-2:30 Actual: 1230-1pm, lunch, 2-3:30

Talk before this went late so we only had 30minutes to start before lunch. Similar delivery as previous though. Still spent more time explaining What and Why about Git and Github using Dropbox and Google Drive as examples.