It's not the cameraman... it's the editor that isn't switching over to the feed from the computer when needed. The cameraman's job is to focus on the speaker.
Cameraman pro-tip: when the speaker is using a laser pointer and saying words like "here", it's best to not put the speaker in the center of the frame. Really anywhere else is better; I'd rather see you turn the camera around and do a dance than look at the speaker flap his face-bits.
+Siddharth Kulkarni You cannot talk about git and use a PC with windows on it... And of course, you don't use Linux, because you can use a mac. So you get a nice computer running unix on it
Top tip for the video operator. We don't need to see the presenter to hear him. But we do need to see what is on the screen that he is talking about. Best example is rebase, not a single view of the branches/graph he was talking about, just a video of his hand.
Why did he try to rebase his [master] mine-branch onto the alice-branch ?? If the mine-branch was already pushed, his newer commits would be replayed but also the sha1-ids would change, creating a conflict between local/master and remote/master. I'm not sure if he did it on purpose (to show how 'unfriendly' git is) or whether he was just careless ? Best practice should be to rebase a feature-branch onto your master ! And NEVER EVER rebase a pushed branch onto a non-pushed branch.
The camera operator may be in love with this guy but the end result makes for a regrettably poor presentation. Also keep the camera focus on either the slides or command line, whichever is the relevant subject at a given moment. There are far too many screen shots of the slides when the discussion is of command line operations, etc..
How did a version control system so horrible ever get so popular? You shouldn't have to know your vcs inside out to do some web development. You need to understand how filesystems work and try not to shoot yourself in a head by confusing some dozens special options for checkout. In mercurial you only need to know half dozen commands or just use gui. Not all developers want to be kernel hackers
Milo Bem, Git is an extremely powerful tool, with an interface to match. If you don't want to invest the time to master the tools of your trade, that's fine (especially if you're not my coworker). It doesn't make Git "horrible" though.
[8:53] How does git data structure enable parallel workflow? Use git log --graph --online , gitk, gitx
[41:59] detached head state with checkout
It's not the cameraman... it's the editor that isn't switching over to the feed from the computer when needed. The cameraman's job is to focus on the speaker.
Cameraman pro-tip: when the speaker is using a laser pointer and saying words like "here", it's best to not put the speaker in the center of the frame.
Really anywhere else is better; I'd rather see you turn the camera around and do a dance than look at the speaker flap his face-bits.
Much was unwatchable for that reason.
same talk where it is done better: ruclips.net/video/fBP18-taaNw/видео.html
@@dran1337 Thanks so much for the link.
right when he was explaining rebase. the reason i watched the first 37minutes
Interesting that he works at Microsoft and uses a Mac. Fascinating in fact.
Indeed, the changes are evident.. :)
+Siddharth Kulkarni You cannot talk about git and use a PC with windows on it... And of course, you don't use Linux, because you can use a mac. So you get a nice computer running unix on it
+Siddharth Kulkarni yeah they are using the light o steve inteligence to to rename with enter ;) and open with CTR O
Fabian Renner I don't agree with the Linux view. My Ubuntu has been a loyal friend.
Mandatory dogfooding hasn't been in force at MS for absolutely ages.
Agree with other comments about the cameraman's job and/or/xor video editors job. But this was a GREAT Talk. Awesome. Thanks !!
44:27 checkout -b doesn't require a delimiter?? whyyyy
Either the camera man or the video editor messed this one up pretty badly. Content was still cool thanks!
No, blue screen of death! Oh, it's just a slide
Learned a lot here. I would like to thank the speaker.
Top tip for the video operator. We don't need to see the presenter to hear him. But we do need to see what is on the screen that he is talking about. Best example is rebase, not a single view of the branches/graph he was talking about, just a video of his hand.
Why did he try to rebase his [master] mine-branch onto the alice-branch ?? If the mine-branch was already pushed, his newer commits would be replayed but also the sha1-ids would change, creating a conflict between local/master and remote/master.
I'm not sure if he did it on purpose (to show how 'unfriendly' git is) or whether he was just careless ?
Best practice should be to rebase a feature-branch onto your master ! And NEVER EVER rebase a pushed branch onto a non-pushed branch.
Awesome talk!
[25:45] someone in the audience just learned how to exit vim and that will be what they take away from this presentation
Look at the audience -- everyone is watching his screen. I bet there's something really interesting happening on it!
He's using cat-file wrong with that tree. He should have used `git cat-file -p c1cacf`.
I would have loved this talk but the camera missed so much of the good stuff. so sad!
is git a vector ?
I learned a lot
I foresee a new rock band from this talk... Alice's Change
The content is great but the guy filming is something else
This seems like a professional git talk, but looks like a high school video editing project. 🤔
14:30
Wow... camera man. Awesome talk though. Thank you!
this is not deep dive just a beginner conf, misleading title and i really wasted my time
Walking around with a glass full of gin, shocking.
He works for microsoft. I'm surprised there wasn't Sunoco Ultra 93 in the glass.
The camera operator may be in love with this guy but the end result makes for a regrettably poor presentation. Also keep the camera focus on either the slides or command line, whichever is the relevant subject at a given moment. There are far too many screen shots of the slides when the discussion is of command line operations, etc..
Only a Microsoft engineer would *talk* about sex and think it's interesting...
"I work at microsoft so I'm very unix-y" not true!
Why use git if it is so hard to use? Why not just use mercurial if you need a DVCS?
Awful camera
As Alex said, great talk awful recording.
Presentation is ruined by this production... :(
How did a version control system so horrible ever get so popular? You shouldn't have to know your vcs inside out to do some web development. You need to understand how filesystems work and try not to shoot yourself in a head by confusing some dozens special options for checkout. In mercurial you only need to know half dozen commands or just use gui. Not all developers want to be kernel hackers
Milo Bem git has quite some GUI clients and excellent integration to all major IDEs and editors.
Milo Bem, Git is an extremely powerful tool, with an interface to match. If you don't want to invest the time to master the tools of your trade, that's fine (especially if you're not my coworker). It doesn't make Git "horrible" though.
not very useful