I’ve chosen this specific list as part of an effort to foster a shared understanding of commonly used terms. This “glossary” doesn’t exist in a vacuum – it can (and should) continue to be challenged and evolve over time as our understanding changes.
GitHub content on the Revelry Blog: Navigate our lab notes by using the tag system.
I was lying in bed this morning planning the best way to handle a merge conflict I know is coming with a colleague’s PR today, and I realized I’d like to know a couple of tricks for certain situations. Here they are:
Make sure you’re doing this consistently, because down the line it makes a big difference to somebody digging through git history.
If you write tests after you wrote the code, it’s hard to be 100% the tests are legit… If they wouldn’t have failed without the code you just wrote, they’re basically useless.