Git and Github: Working Effectively on a Team


Comments are closed.

Anonymous at 11:55 on 15 Mar 2014

Anonymous at 11:57 on 15 Mar 2014

Kind of a fast overview, looked at the screen a lot

Good talk, lots of information. I might actually go a little slower if you can, if people get lost for a few minutes it could be hard to find the thread again. Would have liked to see a bit on "git add -p", since that's my favorite feature, but if you're doing small fixup commits then it seems like it'd be less necessary. Good job

Best explanation I've heard on how, why and when to use rebase. Thanks.

Good talk, but a lot of ground to cover in an hour.

Good talk, spent a little too long on the "intro-to-git-vocab" (but probably a necessary piece for beginners). I was hoping for more of an in depth discussion of two or three specific team-centric workflows.

Overall, good speaker, good content.

Talk was good. I think that this was a good overview.

Good talk, I thought you spoke a little bit on the quick side and there was a lot of content to get through. Awesome information, and I learned some new things that I'll definitely use.

Good talk. I would like to look into some of the commands more so that we can get some better interaction in repos.

In general, we use push/pull without doing much else. It would be nice to use Git to its full potential.

Interesting talk. The promotion of rebase in a team setting seemed a bit odd, especially from a relatively new git user pov (3-4 months), though it started to get clearer during the Q&A at the end. Still seems like a very specific and potentially harmful practice, but hey, what isn't? Good transition from basic git commands to uses.

Anonymous at 08:02 on 16 Mar 2014

Would be good to discuss tagging commits against tickets. Helps with organization, reduces need to ever rebase.

I've been using Git at a very basic level for just over a year now, and our organization is starting to grow. Soon, I'll need to be working on a team with others and figuring out a work flow that allows us to integrate changes into a codebase via a formal review process. Jeff's presentation introduced some commands that I have been aware of, but wasn't necessarily certain how they work and in which situations they should be used.

The command terminology overview was especially helpful in shedding light on some of these not-really-that-obscure commands, and I'm excited to go back to the office and start fetching changes instead of pulling them, then merging branches only when I'm ready. I'm equally thrilled about understanding the difference between a merge and a rebase, and I'm hoping to start using these more advanced techniques in the future.

Great, great talk.

As someone that's still using svn at work, I appreciated this talk very much.

We're right in the middle of re-assessing our git workflow so this talk couldn't have been more timely. I really appreciated the examples and demos. Git Flow, commit rebase-ing, branch histories, and even the differences between svn and git are a lot more clear and tangible to me now after hearing this talk. My only critique would be a request for more explanation of what problems rebase solves beyond a cluttered history (perhaps also some more detail on how git pull fits in). Thank you very much for the talk!

Anonymous at 18:18 on 16 Mar 2014

As a single developer, I have not used git other than to play around so it was a bit much for me. Still, I enjoyed your talk and can see where adding git as a disciple will only benefit me in the future - especially since I'm looking to rejoin the work force!


- Demystifies and encourages rebase, paving the way for clean commit history
- Liberated us from weird dogmas ("Everyone must use GitFlow")
- At some point in the future, when clean commit log matters bigtime, I will be glad to have seen this talk and will boldly venture into rebase.


- Perhaps should have been titled "How to not be terrified of Rebase, in the interest of a clean commit log" (or something like that)
- In other words, it didn't feel like a holistic look accross Git/GitHub...
--- I don't feel that it left me as someone who better understand the whole and depth of something I already knew.