Not using the Git Command Line

Good explanation of why things were important, and concept of narration. Could do with more clearer separation of points made.

Thank you Nigel. Great use of slide layouts, and useful knowledge (I've not used sourcetree, but will be investigating it as I use tortoisesvn). The slides could have been animated so as to not have everything on screen at once, but again it's a 10 minute talk.

Good for people who do use the command line to see how useful a GUI tool can be. Talk overran so I think we missed some of the conclusions.

Bit rushed and could have less information. Howeber very detailed overall.

I loved this talk, it was thoughtful and thought provoking. I think the visibility point is really important. You gave me a better understanding of git GUIs, too!
I liked that you walked to the other side of the presentation instead of walking in front to point.
For a lightning talk it might have been beneficial to condense some of the points!

Well paced but felt like there was too much obvious information which made it hard to pick out out the important points. Suggest using less cluttered slides with clearer headlines of main points.

Good talk with many good points, would have been nice to introduce other tools that make working with git from a gui l easier.

Really enjoyable talk. For me the comparison between the written directions and the graphical map really ran the idea home that using a GUI is very useful. Thank you for the insight.

Git comes with a sourcetree equivalent called gitk granted it's not as nice looking as sourcetree but it is fast + reliable

Emacs and sublime with their respective packages also have a good half way house between GUI and cli that I think goes under appreciated in terms of sane defaults and discoverability

I like to switch between Terminal, Sublime, VScode, gitk and Fork (similar to sourcetree) at work and it still feels like they all have their strong points, even though they overlap

A talk that explores the full ecosystem of git tools and their trade offs/ strengths would be cool, atom for example has a git 'timemachine' with a intresting UI

I seem to switch between multiple Git clients, and I've never really understood why I do that until now. I use the command line proper, gitk (very basic graphical browser that ships with git itself), the one built-in to VS Code, and SmartGit (a full-blown GUI and a slightly better user experience than SourceTree, IMO). Why so many? I think Nigel's talk gave me the answer. It depends on the context. Sometimes I just need to make tiny atomic commits as quickly as possible, other times I want to understand the bigger picture and read the story of an application's progress. Different tools fulfil these different roles. Another talk that got me thinking...

Great talk. Well delivered. Lots of valid points about things I've not really thought about (e.g. what times are people making commits, are they working all night, etc).

I think you might have convinced a CLI dinosaur like me to look into source tree!

My only tip for improvement is to slim down the talk.

An interesting talk on git GUIs, particularly liked the idea of using git source tree to monitor project/developer progress to detect potential issues early on.

A possible improvement could be slightly less cluttered slides.