In celebration of my newest book: Git For Programmers I’m starting a short series of blog posts on some of the more interesting features of Git.
You already know Git
These posts assume you know what Version Control is and why you want it. I even assume you’ve been exposed to Git because Stack Overflow says 93% of programmers have. So these posts will be the fun stuff.
Let’s dive in to one of the most confusing aspect of Git for many programmers: Rebasing. When you say rebasing, many programmers run from the room pulling their hair and crying.
But Rebasing is really not that bad. In fact, it is pretty straight forward.
Let’s say you are working on a branch (you do your work on a branch, right??) and you want to merge the main into your branch to reduce the probability of conflicts later.
If your feature branch branched off of the latest commit from main, no problem, you do the merge, and Git will do a fast forward for you…
This is a repost from 2009. It talks about breast cancer, but applies equally well to Covid testing, given the high percentage of false positives (not to mention the more worrisome false negatives). We simply are not wired well for probability…
1% of women at age forty who participate in routine screening have breast cancer. 80% of women with breast cancer will get positive mammographies. 9.6% of women without breast cancer will also get positive mammographies.