In November, we had another lightning talk event at .NET Oxford, where I did a talk on Developer Productivity. I summarised the talk, in my blog post about the night, but promised that I'd do a full blog post about my talk - so here it is!

One of my recent blog posts - "Git GUIs versus the CLI", discussed why I think that a GUI is far better suited for source control than the CLI. However ... being a big command line fan (albeit, perhaps not always for source control!), the last thing I wanted was to come across as anti-CLI! Far from it! So I thought a post about the CLI, together with a few tips to help you get the most out of it was in order!

I quite often hear experienced Git users say that you should always use the command line for Git, and you should try to avoid using Git GUIs. Whilst I understand the reasons given, I also think it's a huge generalization that unfairly sees Git GUI users as unlikely to really understand Git properly. I certainly know Git very well, and honestly think I'm far faster and more efficient in a Git GUI than I could possibly be on the command line - and I'm certainly not slow in the CLI.