Comments (13)
85 minutes actual
from git.
Previous actual was incorrect. I mistakenly lumped the time together with ga-wdi-boston/git-github-fork.
Actual was 65 minutes.
from git.
70 minutes.
from git.
70 minutes is practically a 2 actual
from git.
77 minutes actual (break included)
from git.
70 inc break
from git.
I'm going to remove the prepared label until we've merged changes and closed other open issues. Apologies @payne-chris-r.
from git.
@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"?
from git.
I'll adjust the calendar. Thanks @payne-chris-r
from git.
1 Actual. 55 minutes. It went shorter than I anticipated, but went long on github lesson.
from git.
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.
from git.
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.
from git.
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.
from git.
Related Issues (20)
- Don't use `git add .` HOT 6
- Explain why one should not use `git commit -m "<one line message>"` HOT 10
- Show developers `git rm` to stage a delete of file HOT 3
- Change formatting HOT 3
- Typo in 2nd Ned Stark paragraph
- Adjust order of git stages HOT 5
- update license HOT 1
- PVD Delivery HOT 2
- Rename to `git` HOT 1
- "livelihood" typo in Why git section
- Branching your dreams lab HOT 2
- learn git branching
- Should we explain version control more in the README? HOT 2
- Should `Learn Git Branching` tutorial be used? HOT 2
- Should `git commit -m` be taught or be framed less negatively? HOT 2
- Add a step that they must not be in the `git` repository before creating the folders
- Just thought of a potentially helpful analogy HOT 1
- Dead link HOT 1
- Demo git branching tutorial first level HOT 6
- Mention `git log` options for visualizing branches? HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from git.