Git for Programmers: Master Git for effective implementation of version control for your programming projects

I really like this book and was excited to see a new title published the topic since GIT is the defacto standard in software development. The book addressees the topics and will be a good reference to keep in my Kindle library. The problem I have is the switching between command line, Visual Studio Code and Docker Desktop loses some of the continuity and flow the book otherwise has. For example, if the read prefers to uses the Mac/os or linux command line and Atom as an editor, it is silly to have search where to read next to skip over the other two methods. Sure, perhaps somedays I may be assigned to a project where VSC is used, but I would rather but a dedicated book that ignores the other two ways.Overall, nice book from this author. I look forward to seeing more work from him as he is a valuable writer and instructor in the IT community.

The author uses three interfaces: VS Code, Github Desktop, and Git CLI; to show some of the basic commands you'll often use with version control using git. Some of the CLI commands in the code examples aren't accurate (committing and adding a file in a single command), and some of the most interesting stuff doesn't even include CLI examples or is a mix of both GUI interface and CLI.A book on the topic, preferably for advanced team-oriented practices, deserves to be published - but this book doesn't fit the bill, especially for the price-tag it's currently at.I would suggest saving your money and using documentation or stackoverflow.

Terrible book.Author has no idea how to teach.Let me give you an example:Author recommends to install shell for pretty looks. I don't want that, so I skipped it and used the original cmd. It turns out whenever nothing works unless you google yourself why you're getting an error with as simple as a command git status, it gives you an error if you don't use git init. The author does not mention this, he assumes you should know this, yet he mentioned he does not expect to know anything about git.The list goes on, use git add name, guess what you get another error, good luck with you fixing this on your own.The author does not expect you face these issues ? still on page 21,Page 25 the author said click on staged, you look at his figure and there's no such a freaking button shown, where the heck is this button that I should click onyou want me to continue ...Don't waste your money

It was somewhat timely that I learned about this book, as I was starting to look for resources for some new team members who are relatively new to git and some of the common workflows (like gitflow, that this book demonstrates). Fortunately, I was asked by the publisher to give it a read and provide my feedback.The book's initial chapters introduce git, and show how to use several different clients (command line, Visual Studio, and GitHub desktop). I wish the book mostly lead with the command line for everything, as this is the lingua franca for git users, and all GUI tools basically just wrap the CLI in their own ways. Knowing and growing comfortable with the command line is critical for easy migration between platforms and git providers. I was disappointed that Visual Studio Code wasn't used instead, as this popular open source tool is available on all common platforms (Mac, Windows, Linux) and is probably a better tool than the Windows centricity of Visual Studio.Some definite Pros in this book include using some working examples, so you can directly experience the basics (creating repos, branching, merging, pull requests, etc), and experience some of the really critical techniques of rebasing, amending, and cherry picking commits.There is enough in the book to also give the new practitioner an understanding of how to be clear of the status of your current code, review logs in different ways, and use various means to provide metadata to better organize your code (e.g. notes and tags).The book ends with some common use cases around finding bad commits and fixing common errors (e.g. wrong messages, commit mistakes, naming issues, etc.).I knock a star off for some unfortunate editing reasons. There are some typos in the text, and in at least one section (Chapter 10), while teaching the use of stash, the section on recovering/reapplying the stash is missing. If you are patient, the challenge section demonstrates how to use apply, but if you just go by the table of contents or are skipping the challenge/quizzes, you'll miss it.Editing aside, the author does a fine job of communicating the basics in a friendly, incremental way, and the majority of the text would provide a good starting place (or refresher) for the most common git work you're likely to encounter day to day.

The forward is great! It states what I’ve felt: that git has a ridiculous number of rarely used commands, each having a large suite of options. It goes on to state that many expert developers are afraid to admit that they’re not as versed in git as “expert” should imply. Hey! Is that me?This book is excellent. But first, a couple of cons …The introduction indicates that the book does not formally support Linux, saying that almost all of Git is the same on all platforms anyway. Yet I find git on Windows to be annoying due to backslash directory separators and missing *nix commands. Thus, on Windows, my CLI once was gitBash, or today’s WSL 2. The former is *nix. The latter is actual Linux on Windows 10. There is no mention of these or the older bash shell in the book.The book leverages Visual Studio 2019 but has no words about Visual Studio Code. The latter installs on Linux, by the way.Those nits aside, this book is well-done. At times, I’ve found myself in a cold sweat due to a broken commit deeper in the history, or a rebase against the wrong branch. I learned to repair such things after periods of shaky angst. With this book, fear of stroking out would have diminished. Namely, Chapter 11: Bisect and Commit, and Chapter 12: Fixing Mistakes, explain accessible magic.If you think you know already git, buy this book anyway. Those two chapters reinforce applied git knowledge.

Gli argomenti sono trattati superficialmente e il modo in cui gli esempi sono riproposti contemporaneamente in tre modalità diverse GitHub, Visual Studio e linea di comando possono confondere. Consiglio altri testi ad esempio ProGit