Elegant Source Control (3): Using Git Rebase Gracefully, Locally
One thing I have to rant about: I see tons of Merge commits in projects, but that's not how Merge is meant to be used. Most of the time, you should be rebasing.
5 posts
One thing I have to rant about: I see tons of Merge commits in projects, but that's not how Merge is meant to be used. Most of the time, you should be rebasing.

As you keep using Git, understanding how it actually works makes many problems easier to grasp — rebasing, divergence, and so on. I recommend every Git user understand how Git works. Understand it — no need to master it. So a light read is all you need, and I won't go deep either.

In everyday development, as a tech manager I keep seeing developers who freeze up on conflicts or even lose code, commit histories flooded with Merge commits, careless and chaotic commit messages, and so on. So I want to write this series to help developers use Git quickly and gracefully.

OmniGraffle Pro 7 – Innovative productivity. Intuitive design. Powered by humans. Design and build incredible graphics, diagrams, flowcharts, website and app wireframes inside OmniGraffle 7—from simple to infinite, creating ultimately scalable and easy-to-use applications in endless applications where you can imagine everything, for precise, beautiful graphics.

A project manager should have a technical background. In my view, to manage or communicate with technical people you need fairly specialized technical knowledge; otherwise you cannot speak their "jargon", let alone share a "common language". Most technical people have strong personalities and their own ways of thinking, so without a technical background your opinions will be unconvincing and you will be easily fooled by dominant technical people.
